NewsCryptoMatt Corallo Puts Bitcoin (BTC) Cleanup Fork BIP-54 Odds at 80%

Matt Corallo Puts Bitcoin (BTC) Cleanup Fork BIP-54 Odds at 80%

Author: CryptoNewsNet·

Key Takeaways

  • •Matt Corallo estimates roughly an 80% probability that the Great Consensus Cleanup (BIP-54) becomes Bitcoin's next soft fork, while stressing that no formal timeline has been set.
  • •The proposal targets four known vulnerabilities: poison blocks, time warp bugs, Merkle malleability, and duplicate coinbase transactions.
  • •Paul Sztorc, co-founder and CEO of LayerTwo Labs, dismissed the upgrade as a 'janitorial' maintenance fork that adds no new functionality.
  • •A developer survey Sztorc conducted at TABconf found the earliest activation estimate at September 2027, with most respondents pointing to 2028 or later.
  • •Taproot, activated in November 2021, remains Bitcoin's most recent soft fork, and Corallo argues BIP-54 could produce a reusable activation playbook for stalled proposals such as OP_CAT and OP_CHECKTEMPLATEVERIFY.
Matt Corallo Puts Bitcoin (BTC) Cleanup Fork BIP-54 Odds at 80%

Corallo: Roughly 80% Odds for the Next Soft Fork

The Great Consensus Cleanup (BIP-54), a consensus-cleanup specification first proposed in 2019 and co-authored by long-time Bitcoin ($BTC) developer Matt Corallo, has emerged as the leading candidate for the network's next soft fork. Appearing alongside MARA Foundation Head Isabel Foxen Duke on MARA Foundation TV, Corallo gave the upgrade roughly an 80% chance of coming next, while stressing that no formal timeline has been set. A Bitcoin Improvement Proposal (BIP) is the numbered-document format through which consensus changes are drafted and debated, and a soft fork is a backward-compatible tightening of those rules — non-upgraded nodes continue to accept blocks produced under the stricter set, which is why it is the route Bitcoin's recent protocol upgrades have taken.

The document's stated purpose is to strip what its own text calls the “cruft” from Bitcoin's consensus design — changes that have historically been sidelined even though they “fix some stuff that everyone agrees are problems,” in Corallo's words.

Four Legacy Bugs in the Crosshairs

The specification names four specific targets:

  • Poison blocks would let a miner craft a block that exploits performance bottlenecks and deliberately slows validation for every other node operator.
  • Time warp bugs exploit a loophole in the two-week difficulty adjustment window, allowing a miner with a majority of the network's mining power to manipulate block timestamps and issue blocks faster than the schedule intends.
  • Merkle malleability turns a size coincidence — a 64-byte transaction matching the exact data size of an internal Merkle tree node — into a way to forge proofs that trick light clients into accepting fake transactions.
  • Duplicate coinbase transactions stem from historical design quirks that allowed duplicate transaction IDs to resurface at future block heights, a path that could overwrite existing coins or disrupt ledger accounting.

Corallo described the backlog plainly: “There's a laundry list of things we know of that we really need to clean up. All of these issues are real concerns that could impact Bitcoin ($BTC) negatively, but they're not like, 'Oh, the sky is falling.'” None of these repairs can ship like a routine patch: consensus changes take effect only through coordinated activation across miners and the wider node ecosystem, which is why fixes with broad technical agreement can sit for years awaiting a deployment window.

The network's last soft fork to activate was Taproot, in November 2021. Bitcoin's price moved 3.8% over the past 24 hours, a trading session that had little to do with any of this.

Sztorc Calls It a “Janitorial” Fork

The reception is where agreement frays. Paul Sztorc, co-founder and CEO of LayerTwo Labs, called BIP-54's potential activation “kind of depressing, since it is a janitorial maintenance fork that doesn’t do anything” in a post on X. In a second post, published after he surveyed developers at TABconf in Atlanta, Sztorc noted that Bitcoin's “best and brightest” predominantly expect the Great Consensus Cleanup to be the network's next soft fork anyway, with the earliest estimate in September 2027 and most pointing to 2028 or later.

His objection is less about the bugs than about what a maintenance fork does to the upgrade pipeline. Since Taproot activated in 2021, Bitcoin's community has spent years in gridlock over protocol changes — a friction its critics frame as “ossification” — and broader proposals such as OP_CAT (BIP-347) and OP_CHECKTEMPLATEVERIFY (BIP-119) have struggled to reach ecosystem-wide consensus.

The upgrade path that carried Segregated Witness into the protocol predates that freeze, and Corallo's account of the shift is direct: soft forks have always involved technical hurdles, but he has watched political and social friction become just as relevant. Taproot itself consumed months of argument over activation, with miner-signaling thresholds pitted against mandatory user flag days.

That history is why Corallo frames BIP-54 as more than cleanup. “In every recent soft fork, there's also been a bunch of drama about activation mechanisms,” he said, adding that a completed cleanup fork would hand developers a deployment playbook they could “copy and paste and reuse” to head off the same drama next time. In his telling, BIP-54 is as much a test of whether Bitcoin can still agree at the social layer as it is a code cleanup.

@Truthcoin · X post
Called.
View on X

A Rehearsal, Not a Feature Release

For protocol watchers, the number that matters most in the BIP-54 debate is not Corallo's 80% but the calendar inside Sztorc's TABconf survey: even the earliest estimate puts activation in September 2027, and the consensus view stretches to 2028 or beyond. Measured against the specification's own text, that gap makes the Great Consensus Cleanup less a feature release than a rehearsal, and its most durable output may be the deployment playbook Corallo describes — a path from proposal to activation that OP_CAT and OP_CHECKTEMPLATEVERIFY could follow without relitigating every argument. Until a formal timeline exists, the observable milestones are procedural: agreement on an activation mechanism and, eventually, miner signaling — the same steps that carried Taproot from proposal to protocol. If BIP-54 clears that bar, the ossification argument loses force. If it stalls, the case that Bitcoin can no longer ship consensus changes hardens.