[BIP Draft] Testnet 5

The recent discussions on the Bitcoin Development Mailing List have raised questions about the future of testnet versions and their implications for blockchain development. A significant point of concern is whether updates for testnet4 will still be pursued or if efforts will transition towards newer versions. Detailed analysis can be found in the documentation provided at testnet4 fixes.

A technical discussion has also unfolded regarding the potential outcomes when a block hash is used as an x-value for a public key in transaction scripts. This method could result in outputs that are either spendable if they correspond to a valid secp256k1 point or unspendable if they do not align with the curve requirements. For instance, certain configurations were highlighted where outputs would be unequivocally unspendable due to the script structure or data size discrepancies such as using 32 bytes instead of the typical 33 or 65 bytes for stack pushes followed by OP_CHECKSIG.

Additionally, the conversation touched on the pace at which new testnets and corresponding coins are adopted and listed on exchanges. Historically, there has been a lag between launches and listings, but recent trends indicate quicker listings. This rapid adoption could incentivize miners to accumulate initial blocks before selling them post-listing for profit.

Another focal point was whether testnet5 would involve any premine, contrasting previous setups like those discussed in a prior attempt to establish testnet5, outlined at BitcoinTalk discussion on testnet5. The community seems inclined towards simplifying codebases by potentially removing certain existing rules from earlier testnets, although fully deprecating older versions like testnet3 and testnet4 might require substantial time and consensus within the development community.