BIP-54 explained: Bitcoin's consensus cleanup soft fork

Bitcoin developers increasingly expect the Great Consensus Cleanup, a proposal numbered BIP-54, to be the network's next soft fork, Unchained reported on 2026-11-04. The proposal fixes four old weaknesses in the rules every node enforces. This article looks at what each fix changes, why all of them can ship as a soft fork, and why developers see the upgrade as a rehearsal for harder debates.

The change in one paragraph

BIP-54 was first proposed in 2019. It adds no new features. Instead it closes four known gaps in Bitcoin's consensus rules: poison blocks, the time warp bug, Merkle malleability and duplicate coinbase transactions. Matt Corallo, a long-time Bitcoin developer and co-author of the proposal, discussed it on MARA Foundation TV with MARA Foundation Head Isabel Foxen Duke. He described the flaws as genuine risks, but not an emergency.

In his words: "There’s a laundry list of things we know of that we really need to clean up".

Under the hood: four rules that get tighter

A soft fork only narrows what the network accepts. Blocks that follow the new rules still look valid to old nodes, so the network does not split as long as most miners enforce the stricter version. That property is why a cleanup like this is easier to deploy than a change that adds new abilities. Each of the four fixes is, at heart, a new restriction:

• Poison blocks. Today a miner could craft a block that deliberately hits slow paths in node software. Rivals spend longer checking it, which hands the attacker a brief head start on the next block. The fix limits the kinds of block content that make validation unusually expensive.
• Time warp bug. Mining difficulty is reset over a two-week window based on block timestamps. A miner group with majority hashrate can bend those timestamps so the system thinks blocks are slow, lowers difficulty and lets new blocks arrive faster. The fix constrains which timestamps are allowed around the window boundary.
• Merkle malleability. A Merkle tree is how a block commits to its list of transactions. Because a 64-byte transaction is exactly the size of an internal tree node, the two can in theory be confused, letting an attacker build fake proofs that fool light clients. The fix removes that ambiguity.
• Duplicate coinbase transactions. The coinbase is the first transaction in each block, the one that pays the miner. Old design quirks mean identical transaction IDs can come back at future block heights, which could overwrite existing coins or confuse ledger accounting. The fix makes each coinbase unique.

None of these changes alter how ordinary payments are built. They tighten edge cases that only a miner or a sophisticated attacker could exploit. That is also the core of the criticism: LayerTwo Labs co-founder and chief executive Paul Sztorc wrote on X that activating BIP-54 would be disappointing because it is pure maintenance with nothing new.

Who is affected

Miners are the group whose behaviour actually changes. The time warp and poison block fixes take away tools that only block producers can use, and miners will need software that enforces the new rules. Node operators would upgrade to validate blocks under the tighter rules, while older nodes would keep following the chain.

Light clients, such as many mobile wallets that check proofs instead of full blocks, benefit most directly from the Merkle fix. Everyday users holding or sending bitcoin should see no difference in how transactions work. Developers are a quieter group in the story: Corallo noted that many current contributors have never shipped a soft fork, since Taproot in November 2021 was the last one.

Why activation is the real test

Writing the code is the smaller part of a soft fork. The harder part is agreeing how the network switches the new rules on. Taproot activation took months of argument over miner signaling thresholds versus mandatory user flag days. In a signaling approach, miners mark blocks to show readiness and the rules lock in once enough do. In a flag day approach, nodes enforce the rules from a set point whatever miners signal. Each shifts power differently between miners and node operators.

Corallo said political and social friction now weighs as much as technical hurdles. Since Taproot, more ambitious ideas such as BIP-347, known as OP_CAT, and BIP-119, known as OP_CHECKTEMPLATEVERIFY, have not reached consensus, a stalemate often called ossification. His hope is that a low-controversy fork lets the community settle an activation method once and reuse it later. Unchained framed BIP-54 as a test of whether Bitcoin can still agree at the social layer, not only a tidy-up of code.

Status and next steps

There is no formal timeline. Corallo put the chance that BIP-54 is the next change at 80%. Sztorc's informal survey of developers at TABconf in Atlanta pointed the same way, with the earliest guess at September 2027 and most answers at 2028 or later. Until an activation method is chosen and released in node software, the existing rules and their known gaps remain in place.

Sources

• Unchained, 4 Nov 2026

AI wrote this summary from the primary documents and reports cited above. It went live automatically after checks that figures match those sources and nothing is copied; there was no human review. It explains a protocol or rule change and is not investment advice.