Bitcoin's Testnet5 lets miners trial four proposed BIP54 Consensus Cleanup rules
In brief
- Testnet5 enforces four proposed BIP54 Consensus Cleanup rules from block one.
- Miners can build Testnet5 blocks with their own software, without signet's signing challenge.
- BIP95 drops Testnet4's 20-minute rule and raises minimum difficulty to about 1 million.
- Bitcoin Core support remains an unmerged patch; Sparrow's integration proposal is still open.
- BIP54 remains only a proposal; mainnet activation would be a separate process.
What miners can test now
Bitcoin Inquisition's signet already enforced the BIP54 rules. The catch? Producing blocks there also required miners to pass a signing challenge on top of proof of work. On Testnet5, independent miners and pools can build blocks with their own software and see whether other nodes accept them (no signing challenge involved).
The four rules are fairly narrow. One caps certain signature operations in ordinary transactions, which limits how long a block can take to verify. Another restricts timestamps at the start and end of each difficulty period so miners can't artificially drive difficulty down. A third rejects transactions measuring exactly 64 bytes once witness data is removed, closing an ambiguity in proofs of transaction inclusion. The fourth makes each new mining reward transaction unique by requiring its locktime to equal the block height minus one (and requiring that locktime to take effect). Pool software usually builds that reward transaction, so operators can use Testnet5 to check it applies the new rule.
Testnet5 is a test network, and BIP54 is still a proposal; mainnet activation would be a separate process.
Why the 20-minute rule is gone
Testnet4 let miners drop to minimum difficulty if a block's timestamp was more than 20 minutes after the previous one, except at the start of a difficulty period. The BIP95 specification says competing blocks mined under that exception caused frequent short reorganizations. It's fixed bluntly. Per BIP95, Testnet5 removes the 20-minute rule altogether and raises the minimum difficulty from 1 to about 1 million, a floor its authors picked to slow block production before difficulty adjusts while letting a single specialized mining machine keep the chain running.
Core and Sparrow aren't there yet
Bitcoin Core's Testnet5 support is an unmerged patch. Its author reported that testers can build it and sync by manually connecting to a peer. The proposal targets Core's 32.x branch and still has to be merged and shipped in a public release; Bitcoin Core 32.1, the latest release as of Nov. 18, predates the Testnet5 integration build.
Sparrow's wallet integration proposal opened late on Nov. 17. It'd let users select Testnet5 and add two public Electrum servers to connect to the chain. A Sparrow collaborator reported on Nov. 18 that the wallet's Silent Payments feature worked in tests against both servers, according to CryptoSlate. The proposal depends on an update to Sparrow's Drongo library and remains open.
Frequently asked questions
What is Testnet5 and how is it different from Bitcoin Inquisition's signet?
Testnet5 is a Bitcoin test network that enforces four proposed BIP54 rules from block one. Bitcoin Inquisition's signet already enforced those rules, but producing blocks there also required a signing challenge on top of proof of work. On Testnet5, miners and pools can build blocks with their own software without that requirement.
Does Testnet5 mean BIP54 is activating on Bitcoin mainnet?
No. Testnet5 is a test network, and BIP54 is a proposed set of rule changes. Mainnet activation would be a separate process.
Why did Testnet5 drop Testnet4's 20-minute difficulty rule?
The BIP95 specification says competing blocks mined under Testnet4's minimum-difficulty exception caused frequent short reorganizations. Testnet5 removes the 20-minute rule and raises minimum difficulty from 1 to about 1 million, while keeping it low enough for a single specialized mining machine to keep the chain running.


