Historical report: November 5, 2026, at 06:46:03 UTC+08:00.
Bitcoin’s next soft fork could focus on longstanding flaws rather than a headline-grabbing feature. The proposed Great Consensus Cleanup, or BIP-54, targets four vulnerabilities—and co-author Matt Corallo sees it as a possible rehearsal for how the network handles future upgrades.
Speaking on MARA Foundation TV with Isabel Foxen Duke, head of the MARA Foundation, the longtime Bitcoin developer put the chance of BIP-54 being the network’s next soft fork at 80%. That is his assessment, not an agreed roadmap: no formal activation timeline had been established.
What the cleanup would address
First proposed in 2019, BIP-54 aims to resolve consensus-rule problems that have historically been sidelined:
- Poison blocks: A miner could create a specially crafted block that exploits performance bottlenecks, slowing other nodes’ validation and gaining a temporary advantage over competitors.
- Time warp bugs: Miners controlling a majority of hashrate could manipulate block timestamps within Bitcoin’s two-week difficulty-adjustment mechanism, artificially speeding up block issuance.
- Merkle malleability: Because a 64-byte transaction is the same size as an internal Merkle tree node, an attacker could theoretically forge proofs that trick light clients into accepting fake transactions.
- Duplicate coinbase transactions: Historical quirks allowing duplicate transaction IDs would recur at future block heights, potentially overwriting existing coins or disrupting ledger accounting.
Corallo described these as real concerns, but not an immediate catastrophe: “All of these issues are real concerns that could impact Bitcoin negatively, but they’re not like, ‘Oh, the sky is falling.’”
A deployment rehearsal, not an agreed plan
The proposal’s significance goes beyond maintenance. Corallo suggested it could give developers who have never participated in a soft fork practical experience—and establish an activation playbook that later upgrades could reuse.
Bitcoin’s community spent months debating how Taproot should be activated, including disputes over miner-signaling thresholds and mandatory user flag days. Taproot activated in 2021; subsequent years brought continued gridlock over protocol changes.
That friction is often discussed in terms of “ossification.” Broader proposals, including OP_CAT (BIP-347) and OP_CHECKTEMPLATEVERIFY (BIP-119), have struggled to secure ecosystem-wide consensus. Corallo said political and social obstacles have become as relevant as technical ones.
His hope is that working through BIP-54’s activation disputes could make future deployments less contentious. That remains an argument for the proposal, not evidence that agreement has already been reached.
Support for maintenance is not universal
On X, LayerTwo Labs co-founder and CEO Paul Sztorc called BIP-54’s possible activation “kind of depressing, since it is a janitorial maintenance fork that doesn’t do anything.”
Yet Sztorc reported that developers he surveyed at TABconf in Atlanta predominantly expected the cleanup to be Bitcoin’s next soft fork. The earliest estimate he cited was September 2027, with most pointing to 2028 or later. Those were expectations from his survey, not a deployment schedule.
The distinction matters: BIP-54 offers specific fixes, while its potential role as a test of Bitcoin’s ability to coordinate upgrades remains unproven.
Source disclosure: The original identifies André Beganski as a senior content manager at the MARA Foundation who previously worked for Decrypt.