Bitcoin miners now have access to Testnet5, a new testing network where they can validate their software against four proposed changes to Bitcoin's consensus rules. Bitcoin Core and Sparrow Wallet are preparing support for the network at the patch stage.
The Bitcoin Improvement Proposals repository recorded Testnet5's first block on November 17, three days after it was mined. The four rule changes are collectively known as BIP54, or Consensus Cleanup, and were previously enforced only on Bitcoin Inquisition's signet, which requires miners to satisfy additional signing challenges beyond proof of work.
What the Four Proposed Rules Change
The proposed changes address several aspects of Bitcoin's block validation and mining:
- Two rules limit the computational work certain blocks can impose on nodes and restrict how miners can manipulate timestamps to influence difficulty adjustments.
- One rule caps signature operations in regular transactions to limit block verification time.
- One rule restricts timestamps at the start and end of each difficulty period to prevent miners from artificially lowering difficulty.
- One rule rejects transactions that measure exactly 64 bytes after removing witness data, closing an ambiguity in transaction inclusion proofs.
- One rule makes each mining reward transaction unique by requiring its locktime to equal the block height minus one.
Changes to Testnet Parameters
Testnet5 differs significantly from its predecessor, Testnet4. The minimum difficulty has risen from 1 to approximately 1 million to slow early block production before difficulty adjusts naturally. This higher floor keeps the test chain running while remaining low enough for a single specialized mining machine to maintain it.
Testnet5 removes the 20-minute rule that allowed miners to drop to minimum difficulty if a block's timestamp exceeded 20 minutes after the previous one. According to BIP95, competing blocks mined under this exception caused frequent short reorganizations on Testnet4.
Current Implementation Status
Early testers can build a Bitcoin Core patch and sync to the network by manually connecting to a peer. The proposal targets Core's 32.x branch but still requires merging and shipping in a public release. Bitcoin Core 32.1, the latest release as of November 18, predates the Testnet5 integration.
Sparrow Wallet opened its integration proposal on November 17, which would allow users to select Testnet5 in the wallet and connect to public Electrum servers. A collaborator reported on November 18 that Sparrow's Silent Payments feature worked in tests against both servers. The proposal remains open and depends on an update to Sparrow's Drongo library.

