Bitcoin’s Next Soft Fork May Be a Practice Run for Future Upgrades

Preface

Bitcoin’s next protocol upgrade may focus less on adding new features and more on addressing problems that have lingered in its consensus rules. Longtime Bitcoin developer and BIP-54 co-author Matt Corallo estimates there is an 80% chance that the Great Consensus Cleanup, first proposed in 2019, will be the network’s next soft fork. The proposal targets four vulnerabilities: poison blocks, time warp bugs, Merkle malleability and duplicate coinbase transactions.

None of these issues is described as an immediate crisis, but each could create risks for Bitcoin’s reliability or security. The proposal may therefore serve two purposes: improving the protocol and giving developers and the wider community a practical chance to work through the social and technical challenges of activating a soft fork. Its significance may lie as much in how Bitcoin reaches agreement as in the code it changes.

Lazy bag

The Great Consensus Cleanup, also known as BIP-54, is a proposed maintenance upgrade aimed at four longstanding weaknesses in Bitcoin’s consensus design. Matt Corallo says there is an 80% chance it will be the next soft fork, although no formal timeline has been established. The proposal could also give developers a practical opportunity to rehearse soft-fork deployment and help establish a reusable approach for future upgrades. Critics, including LayerTwo Labs co-founder and CEO Paul Sztorc, consider the proposal unambitious. Yet in a community where protocol changes can become contentious, a successful cleanup could demonstrate that Bitcoin can still coordinate consensus.

Main Body

Bitcoin’s next soft fork could be a comparatively modest exercise in protocol maintenance. The Great Consensus Cleanup, proposed in 2019 and identified as BIP-54, is intended to address flaws and historical quirks in Bitcoin’s consensus rules. Rather than introduce a prominent new capability, it focuses on weaknesses that developers have identified over time. Its prospects have drawn attention because a routine technical upgrade could also test how Bitcoin’s decentralized community coordinates changes.

Matt Corallo, a longtime Bitcoin developer and co-author of BIP-54, has described the proposal as a practical way to address issues that many participants recognize as problems. During an appearance on MARA Foundation TV, he said there is a “laundry list” of items that need cleanup. He characterized them as genuine concerns that could affect Bitcoin negatively, while emphasizing that they do not amount to an immediate emergency. In a separate conversation with MARA Foundation head Isabel Foxen Duke, Corallo put the chance of the cleanup being the next soft fork at 80%. No formal schedule for the proposal’s adoption or activation has been established.

The proposed changes focus on four vulnerabilities. The first, known as poison blocks, concerns the possibility that a miner could craft a block that takes advantage of performance bottlenecks. If successful, this could slow down block validation for nodes across the network, temporarily giving the miner an advantage over competitors. The risk is tied to how nodes process and verify blocks, rather than to an ordinary transfer of funds.

The second issue is the time warp bug, which relates to Bitcoin’s difficulty adjustment mechanism. Bitcoin adjusts mining difficulty over a two-week window. A loophole in the handling of block timestamps could allow miners controlling a majority of the hashrate to manipulate those timestamps. In theory, that manipulation could make new blocks arrive faster than intended. The issue concerns how the network measures time and recalibrates mining difficulty, both of which help maintain the expected operation of the blockchain.

The third vulnerability is Merkle malleability. Bitcoin uses Merkle trees to summarize transactions in a block and provide proofs that a transaction is included. A 64-byte transaction can have the same data size as an internal Merkle tree node. That overlap could allow an attacker to construct misleading proofs and potentially trick light clients into accepting fake transactions. The concern is particularly relevant to systems that rely on compact proofs rather than independently validating every detail of the blockchain.

The fourth issue involves duplicate coinbase transactions. Coinbase transactions are used to create mining rewards and are distinct from ordinary transactions. Historical design quirks made it possible for duplicate transaction IDs to exist. According to the description of BIP-54’s targets, those duplicates could become relevant again at future block heights, creating a risk of overwriting existing coins or disrupting ledger accounting. This is a problem rooted in older design decisions, but its potential consequences make it part of the proposed cleanup.

Together, the four issues illustrate why protocol maintenance can matter even when no single flaw is considered urgent. Consensus rules are followed by independent nodes and miners, so changes need to preserve compatibility and be implemented carefully. A vulnerability that affects validation, timestamps, transaction proofs or accounting can undermine confidence in the system if left unaddressed. At the same time, changing consensus rules requires broad technical review and coordination, which can make even a narrowly scoped upgrade difficult to advance.

Not everyone sees BIP-54 as an inspiring milestone. Paul Sztorc, co-founder and CEO of LayerTwo Labs, described the possibility of activating it as “kind of depressing,” arguing that it is a janitorial maintenance fork that “doesn't do anything.” His criticism reflects a broader question about what counts as meaningful progress: some may prefer upgrades that unlock visible new capabilities, while others prioritize reducing existing technical risks.

Sztorc also reported surveying developers at TABconf in Atlanta. He said Bitcoin’s “best and brightest” largely expected the Great Consensus Cleanup to be the next soft fork. The earliest estimate he cited was September 2027, while most respondents pointed to 2028 or later. These were expectations reported from a survey, not an established activation schedule. The absence of a formal timeline underscores how uncertain the path from proposal to deployment remains.

That uncertainty is tied to a wider debate about Bitcoin’s capacity to change. Since Taproot activated in 2021, discussions over protocol upgrades have often been framed through the idea of “ossification”: the view that Bitcoin becomes increasingly difficult to modify as the network matures. Proposals such as OP_CAT (BIP-347) and OP_CHECKTEMPLATEVERIFY (BIP-119) have struggled to achieve ecosystem-wide agreement. These debates reveal that technical merit alone does not guarantee adoption.

Corallo has observed that soft forks have always required developers to overcome technical hurdles, but he believes political and social friction has become just as relevant. The activation of Taproot, for example, involved months of debate over how the change should be deployed. Participants argued about miner-signaling thresholds and mandatory user flag days, among other considerations. Such discussions can consume time and attention even after developers have produced a technically viable proposal.

For Corallo, BIP-54 could help establish a deployment playbook for future soft forks. He has suggested that the community might use the proposal to work through the disputes surrounding activation mechanisms, then reuse what it learns to reduce friction in later upgrades. In that sense, a soft fork could be valuable not only for its direct code changes but also as an opportunity to refine how Bitcoin participants make decisions.

This perspective gives the Great Consensus Cleanup a dual purpose. At the protocol level, it aims to address four specific weaknesses that have existed for years. At the community level, it could provide a practical test of whether developers, miners, node operators and users can coordinate around a carefully limited change. Success would not necessarily settle disagreements over more ambitious proposals, but it could offer experience that helps future upgrade discussions.

Calling the proposal a practice run does not diminish the importance of its technical targets. Poison blocks, time warp bugs, Merkle malleability and duplicate coinbase transactions each describe a distinct class of concern. A maintenance-focused fork can reduce exposure to such issues while demonstrating how Bitcoin can make changes without abandoning its emphasis on stability. Whether the upgrade moves forward, and when, will depend on continued review and agreement across the ecosystem.

Ultimately, the Great Consensus Cleanup sits at the intersection of security maintenance and social coordination. Its immediate aim is to remove “cruft” from Bitcoin’s consensus design. Its broader significance may be whether the network can agree on a measured upgrade and turn the process into a model for subsequent changes. In a protocol community where consensus is both a technical requirement and a social achievement, that demonstration could be as consequential as the cleanup itself.

Key Insights Table