Thursday, November 19, 2026

Bitcoin miners now have a new testing network, Testnet5, where they can run their software against four proposed changes to Bitcoin’s consensus rules, with support already appearing in Bitcoin Core and Sparrow Wallet at the patch stage.

The Bitcoin Improvement Proposals repository added the record of Testnet5’s first block to the network specification on Nov. 17, three days after that block was mined.

What miners can test

The four changes are collectively known as BIP-54, or Consensus Cleanup. Bitcoin Inquisition’s signet already enforces them, but producing blocks there requires miners to satisfy 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, without that extra requirement.

Two of the four rules 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, restricting how long a block can take to verify. The other constrains timestamps at the start and end of each difficulty period to prevent miners from artificially driving difficulty down.

A third rule rejects transactions that measure 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 by making that locktime take effect.

Pool operators can use Testnet5 to verify that their software, which typically builds the reward transaction, applies the new rule correctly.

Four checks across a mined block

The timestamp check applies to the block header, the locktime check applies to the mining reward transaction, and the transaction list carries separate checks for signature operations and size.

Checks on a mined block
Block segment BIP-54 check Effect
Block header Timestamp limits Guards the difficulty adjustment
Mining reward transaction Reward locktime and sequence Prevents reuse at another block height
Transaction list Signature-operation cap Limits work on non-reward transactions
Rejects exactly 64 bytes Size excludes witness data

The diagram summarizes Testnet5 rules from block one. Mainnet activation would be a separate process, and block segment sizes are illustrative.

Mining pools can use it to check how their own software constructs blocks that meet the proposed rules.

Testnet4 allowed miners to 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. BIP-95 says competing blocks mined under that exception caused frequent short reorganizations, in which one set of recent blocks replaced another.

Testnet5 removes the 20-minute rule altogether and raises the minimum difficulty from 1 to roughly 1 million. The specification’s authors chose the higher floor to slow early block production before difficulty adjusts, while keeping it low enough for a single specialized mining machine to keep the test chain running.

Early testers can build the Bitcoin Core patch and sync by manually connecting to a peer, its author reported. The proposal targets Core’s 32.x branch and still needs 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 and would let users select Testnet5 in the wallet 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. The proposal, which depends on an update to Sparrow’s Drongo library, remained open.

Source link

Exit mobile version