Bitcoin’s proposed Great Consensus Cleanup, known as BIP-54, targets four long-standing weaknesses in the network’s consensus rules. It could also serve as a rehearsal for coordinating future upgrades, according to longtime Bitcoin developer and proposal co-author Matt Corallo.
In Decrypt’s report published on November 5, 2026, at 06:46:03 UTC+8, Corallo put the probability that BIP-54 would be Bitcoin’s next soft fork at 80%. That was his assessment—not an agreed deployment plan. No formal timeline had been established.
What the cleanup would change
First proposed in 2019, the Great Consensus Cleanup addresses what Corallo described as accumulated “cruft” in Bitcoin’s consensus design. Speaking with MARA Foundation head Isabel Foxen Duke on MARA Foundation TV, he characterized the proposal as fixing problems that developers broadly recognize, rather than responding to an immediate crisis.
“All of these issues are real concerns that could impact Bitcoin negatively, but they’re not like, ‘Oh, the sky is falling,’” he said.
The proposal targets four vulnerabilities:
- Poison blocks: A miner could construct a block that exploits performance bottlenecks, slowing other nodes’ validation and giving the miner a temporary advantage over competitors.
- Time warp bugs: A loophole in Bitcoin’s roughly two-week difficulty-adjustment window could allow miners controlling a majority of hashrate to manipulate timestamps and artificially accelerate block production.
- Merkle malleability: A 64-byte transaction has the same data size as an internal Merkle tree node. That overlap could theoretically let an attacker forge proofs that trick light clients into accepting fake transactions.
- Duplicate coinbase transactions: Historical quirks that permitted duplicate transaction IDs will recur at future block heights, creating a vulnerability that could overwrite existing coins or disrupt ledger accounting.
These are proposed consensus-rule repairs, not changes reported as already activated.
Why a maintenance fork could matter beyond the code
Bitcoin’s last soft fork, Taproot, activated in 2021. The years since have brought persistent disagreement over protocol changes, often discussed in terms of “ossification.” Broader proposals such as OP_CAT, or BIP-347, and OP_CHECKTEMPLATEVERIFY, or BIP-119, have struggled to secure ecosystem-wide consensus.
Corallo said technical obstacles have always accompanied soft forks, but political and social friction has become equally relevant. Taproot’s activation process itself involved months of debate over miner-signaling thresholds and mandatory user flag days.
For developers who have not yet participated in a soft fork, Corallo sees BIP-54 as a practical exercise. Agreeing on how to deploy it could establish an activation playbook that later proposals might reuse.
“In every recent soft fork, there’s also been a bunch of drama about activation mechanisms,” he said, expressing hope that a cleanup fork could help resolve those disputes and reduce their recurrence in future upgrades.
Expectations are not a schedule
Not everyone considers a maintenance-focused upgrade a substantial achievement. On X, LayerTwo Labs co-founder and CEO Paul Sztorc described the prospect as “kind of depressing, since it is a janitorial maintenance fork that doesn’t do anything.”
Nevertheless, Sztorc 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; most pointed to 2028 or later. Those were developer expectations, not a confirmed activation timetable.
BIP-54’s potential significance therefore has two distinct parts: repairing specific consensus weaknesses and testing whether Bitcoin participants can agree on an upgrade process. Neither its position as the next soft fork nor its deployment date was settled in the report.
Original source: Decrypt — “Why Bitcoin’s Next Soft Fork Could Feel Like a Practice Run”, published November 5, 2026, at 06:46:03 UTC+8.
Source disclosure: The original article identifies André Beganski as a senior content manager at MARA Foundation who previously worked for Decrypt.