Historical source context: Decrypt published the original article on November 5, 2026, at 06:46:03 UTC+8. The expectations and timelines below reflect that report, not a confirmed activation schedule.
Bitcoin’s proposed Great Consensus Cleanup, known as BIP-54, raises two distinct questions: which longstanding consensus weaknesses should be repaired, and can the community agree on how to deploy those repairs?
According to Decrypt’s report, the proposal dates to 2019 and targets four vulnerabilities. Its significance may extend beyond those fixes: co-author and longtime Bitcoin developer Matt Corallo sees it as a potential rehearsal for future soft forks, particularly for developers who have not yet participated in one.
What the cleanup would address
In an appearance on MARA Foundation TV with Isabel Foxen Duke, head of MARA Foundation, Corallo described a backlog of consensus-design problems that have historically been sidelined. He characterized them as real concerns, but not an immediate crisis.
The report groups BIP-54’s targets into four areas:
- Poison blocks: A miner could construct a block that exploits validation-performance bottlenecks, slowing other nodes’ validation and temporarily disadvantaging competing miners.
- Time-warp bugs: A loophole in Bitcoin’s roughly two-week difficulty-adjustment window could allow miners controlling a majority of hashrate to manipulate block timestamps and artificially accelerate block issuance.
- Merkle malleability: A 64-byte transaction has the same data size as an internal Merkle-tree node. The report describes a theoretical attack in which forged proofs could trick light clients into accepting fake transactions.
- Duplicate coinbase transactions: Historical quirks permitting duplicate transaction identifiers are expected to resurface at future block heights, potentially allowing existing coins to be overwritten or disrupting ledger accounting.
These are proposed repairs to consensus rules, not evidence that the vulnerabilities have been exploited. The supplied report does not provide implementation-level specifications, test results or quantitative estimates of their likely impact.
Why deployment matters alongside the code
Corallo put the probability that the Great Consensus Cleanup would be Bitcoin’s next soft fork at 80%. That was his assessment, not an agreed roadmap: the report states that no formal timeline had been established.
His broader argument was that a relatively focused maintenance upgrade could help establish a reusable deployment process. Bitcoin developers would gain experience not only implementing a soft fork, but also navigating disagreement over activation.
That distinction matters because technical agreement does not automatically settle deployment policy. The article points to months of debate over Taproot’s activation, including disputes between miner-signaling thresholds and mandatory user flag days. Taproot activated in 2021; subsequent proposals such as OP_CAT (BIP-347) and OP_CHECKTEMPLATEVERIFY (BIP-119) have struggled to secure ecosystem-wide consensus amid debate over Bitcoin’s “ossification.”
Corallo’s hope was that resolving activation disputes for BIP-54 could produce a process that later upgrades could reuse. This is a proposed coordination benefit, not a demonstrated outcome.
A maintenance upgrade, not a settled roadmap
Not everyone considered that prospect compelling. On X, LayerTwo Labs co-founder and CEO Paul Sztorc called potential BIP-54 activation “kind of depressing,” describing it as a maintenance fork that “doesn’t do anything.” That is his criticism of the proposal’s scope, rather than a finding that its fixes have no technical purpose.
Sztorc also 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 he cited was September 2027, while most pointed to 2028 or later. Those informal expectations should not be read as an activation commitment.
The central distinction is between the proposed repairs and the hoped-for governance benefit. BIP-54 aims to address specific consensus weaknesses. Whether deploying it would also create a durable playbook for more contentious upgrades remained unresolved in the report.
Source: Decrypt’s original article. The article identifies André Beganski as a senior content manager at MARA Foundation and a former Decrypt contributor.