Hi Andreas, > By the way, testnet3 works great for us (for testing). I consider block > storms a feature, because it tests our code in rough conditions. We had > planned to support both testnets in the forseeable future. > > https://github.com/bitcoinj/bitcoinj/
The "good" news is that testnet4 has very frequent short reorgs. [0] It appears that people are trying to CPU mine by exploiting the rule that difficulty drops to 1 after 20 minutes. For every real difficulty block that's mined, they instantly publish 5 or 6 blocks, right up against the rule that blocks can't be more than 2 hours in the future. Another side-effect of that behavior is that on testnet4 MTP is typically in the future, rather than an hour in the past. Combined with the timewarp attack mitigation rule helped reveal some bugs. [1, 2, 3] There is a potential counter measure [4] that involves re-orging out those low difficulty blocks, though it's just a hackathon proof-of-concept and not likely to be included in Bitcoin Core itself. If anyone were to run it, you'd get even more reorgs to test :-) - Sjors [0] https://fork.observer/?network=4 [1] https://github.com/benjamin-wilson/public-pool/commit/4282233d2f11ceecbd0d142e8292ccc9c37ea999 [2] https://github.com/stratum-mining/stratum/pull/1325 [3] https://github.com/bitcoin/bitcoin/pull/31600 [4] https://github.com/bitcoin/bitcoin/pull/31117 -- 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+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/C899E966-6444-41EC-B977-96CFFCBF936A%40sprovoost.nl.
