Back in February last year I started trying to save testnet from the block storms, modifying my CPU miner to set a timestamp 2 hours into the future on the penultimate block within each difficulty period. Thus the network would be safe from accidental block storms for 2 hours and deliberate block storms for 20 minutes. The hope would be that this would be long enough for an ASIC miner to find a block and thus keep the network safe for the following difficulty period.

I also argued for a soft fork to fix the block storm issue (Lopp had claimed that fixing it required a hard fork).

I didn't run the miner the whole time, so I missed the difficulty adjustment quite a few times, but I do believe I prevented a block storm or two.

Then back in March/April when I was looking to see if it was time to start the miner again, I saw the testnet blocks and mempool were full of crap transactions, so I gave up on the project of trying to save testnet.

I think that Testnet should probably be reset every halving. At the very least to make sure everyone building on testnet has a chance to see if their time-keeping code is leap-year proof 👀 @k00b lol

The fact that testnet coins are accruing value is insane to me.

Why not just have inflation on test net? Then it would never become scarce

I think we should resef the test net every 4 to 5 years so that no complications arises.

I also say it because we can reset it, then why not do it regularly? Why wait till it starts getting some real value.

What a wild story! Scammers gonna scam