Bitcoin launches Testnet5 to let miners test four proposed rule changes
Bitcoin has a new test network called Testnet5. It lets miners try their software against four proposed changes to Bitcoin's rules. The changes are known together as BIP54, or Consensus Cleanup. Testnet5 enforces all four proposed rules from its very first block.
The Bitcoin Improvement Proposals repository, where Bitcoin's technical proposals are tracked, added a record of Testnet5's first block to the network specification on Nov. 17. That was three days after the block was mined.
Key points at a glance
- Testnet5 enforces four proposed consensus rules from block one, all part of BIP54.
- The minimum mining difficulty rises from 1 on the older Testnet4 to about 1 million on Testnet5.
- Testnet5 removes Testnet4's 20-minute difficulty rule entirely.
- Bitcoin Core and Sparrow Wallet still have open Testnet5 proposals at the patch stage.
- Early node syncing and wallet tests have already been reported.
What miners can test on the new network
A testnet is a practice network where developers can experiment without touching real Bitcoin. On Testnet5, independent miners and mining pools can build blocks with their own software and see whether other nodes accept them.
The four rules come from BIP54, the Consensus Cleanup proposal. Bitcoin Inquisition's signet, another kind of test network, already enforces them. But producing blocks there also requires miners to satisfy a signing challenge on top of proof of work. Testnet5 drops that extra requirement.
The four rules work as follows. Two of them limit how much work certain blocks can impose on nodes and how miners can use timestamps to influence difficulty. One caps certain signature operations in ordinary transactions, which limits how long a block can take to verify. The other restricts timestamps at the start and end of each difficulty period, which prevents miners from artificially driving the difficulty down.
A third rule rejects transactions that measure exactly 64 bytes after removing witness data. This closes an ambiguity in proofs that a transaction was included in a block.
The fourth rule makes each new mining reward transaction unique. It requires the transaction's locktime to equal the block height minus one, and requires that locktime to take effect. Pool operators can use Testnet5 to check that their software, which usually builds the reward transaction, applies the new rule correctly.
Why the difficulty floor was raised
On Testnet4, miners could 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. According to the BIP95 specification, competing blocks mined under that exception caused frequent short reorganizations, where one set of recent blocks replaced another.
Testnet5 removes the 20-minute rule and raises the minimum difficulty from 1 to about 1 million. The specification's authors chose the higher floor to slow early block production before difficulty adjusts. They kept it low enough that a single specialized mining machine can still keep the test chain running.
Support is still at the patch stage
Bitcoin Core, the main Bitcoin software, and Sparrow Wallet, a Bitcoin wallet, both have open proposals for Testnet5 support. These have not yet been merged into official releases.
The Bitcoin Core patch targets Core's 32.x branch. Its author reported that early testers can build the patch and sync the network by manually connecting to a peer. The patch still needs to be merged and shipped in a public release.
What is confirmed and what comes next
Confirmed from the sources: Testnet5 enforces the four BIP54 rules from block one, the difficulty floor is about 1 million, the 20-minute rule is gone, and the first block was recorded in the BIP repository on Nov. 17. BIP54 itself remains a mainnet consensus proposal, separate from Testnet5's deployed specification.
Still open: the Bitcoin Core patch has not been merged or released, so wider software support is not yet available. No mainnet activation timeline for BIP54 appears in the sources, and any future activation would be a separate process from the testnet launch.