The testing for quality assurance has already been performed as part of the investigation into the various techniques and possible mitigations. Additional testing is always valuable, but the primary goal of a public demonstration for this would be to help build consensus.
It's a fine line to tread, because on the one hand you do not want to give away the details of how to optimise the attack (whether for maximum profit or for maximum impact), but on the other hand i do think it's necessary to provide some amount of publicly verifiable information to support a soft fork activation proposal.
My approach so far has been to share all details in the semi-private Delving thread that is accessible to a number of experts who would be able to figure it out on their own anyway, and to share a demonstration of an expensive-but-far-from-worst block publicly. This allows anyone to check for themselves that it is indeed possible to craft some slow blocks, and they can refer to an expert to confirm that it can be made much worse. Of course, i remain open to feedback.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/273ith9pPyipCI5hjV6ETFBzFhM4xFN8ptEFK8zc5N-jxGwOBvEn5r9Bt2c9p0A-6-3Bs53gONglzo1QfI4LCIOwkJgR9PWT4iQT_Wbpllo%3D%40protonmail.com.