Bitcoin’s proposed Great Consensus Cleanup is aimed at four longstanding technical flaws. But the debate around it also raises a social question: can developers, miners and users agree on how to activate another upgrade?
In its report published November 5, 2026, at 06:46:03 UTC+8, Decrypt described BIP-54 as a possible rehearsal for future soft forks—not an agreed or scheduled upgrade.
Maintenance as a coordination exercise
Proposed in 2019, the Great Consensus Cleanup targets accumulated problems in Bitcoin’s consensus rules. Longtime Bitcoin developer and BIP-54 co-author Matt Corallo discussed the proposal with MARA Foundation head Isabel Foxen Duke on MARA Foundation TV.
“All of these issues are real concerns that could impact Bitcoin negatively, but they’re not like, ‘Oh, the sky is falling,’” Corallo said.
He put the probability of the cleanup being Bitcoin’s next soft fork at 80%. That is his assessment, not a community decision or an activation commitment. No formal timeline had been established.
Corallo also described the proposal as practical experience for developers who have not yet participated in a soft fork. In his framing, addressing problems that he says everyone agrees need fixing could help establish a reusable deployment process.
The four problems BIP-54 targets
- Poison blocks: A miner could craft a block that exploits performance bottlenecks, slowing other participants’ node validation and gaining a temporary advantage.
- Time warp bugs: Miners controlling a majority of the network’s hashrate could manipulate timestamps within Bitcoin’s two-week difficulty-adjustment window, artificially speeding up block issuance.
- Merkle malleability: A 64-byte transaction has the same data size as an internal Merkle tree node. An attacker could theoretically exploit that ambiguity to forge proofs and trick light clients into accepting fake transactions.
- Duplicate coinbase transactions: Historical quirks permitting duplicate transaction IDs are expected to resurface at future block heights, potentially allowing existing coins to be overwritten or disrupting ledger accounting.
Agreement on fixes does not settle activation
Not everyone sees a maintenance-focused upgrade as a compelling milestone. On X, LayerTwo Labs co-founder and CEO Paul Sztorc called its potential activation “kind of depressing, since it is a janitorial maintenance fork that doesn’t do anything.”
Sztorc nevertheless reported that developers he surveyed at TABconf in Atlanta predominantly expected the Great Consensus Cleanup to be Bitcoin’s next soft fork. The earliest estimate in that informal survey was September 2027, while most pointed to 2028 or later. Those expectations were not an official schedule.
Since Taproot activated in 2021, Bitcoin’s community has faced prolonged disagreements over protocol changes. Debates about “ossification”—whether and how the protocol should continue changing—have formed part of the backdrop to proposals such as OP_CAT (BIP-347) and OP_CHECKTEMPLATEVERIFY (BIP-119), which have struggled to secure ecosystem-wide consensus.
Corallo’s point is that technical work is only part of the challenge. Taproot’s activation process involved months of arguments over miner-signaling thresholds and mandatory user flag days. A comparatively bounded cleanup could offer a chance to work through those procedural disputes again and establish an approach that later upgrades could reuse.
“So hopefully we could do a soft fork to go through that drama, and then copy and paste and reuse it and head off some of that drama [for future soft forks],” he said.
For that reason, BIP-54’s significance extends beyond maintenance: it could test Bitcoin participants’ ability to coordinate a protocol change. Whether it becomes that test, and when, remained unresolved in the report.
Source: Original Decrypt article, published November 5, 2026, at 06:46:03 UTC+8. The article discloses that André Beganski is a senior content manager at MARA Foundation and previously worked for Decrypt.