Mentioned in This Article
1. What is the next Bitcoin soft fork likely to be?
Bitcoin developers appear to be converging on a modest cleanup as the next Bitcoin soft fork: BIP-54, known as the Great Consensus Cleanup, which would repair four long-standing flaws in the network's consensus rules. Matt Corallo, a veteran Bitcoin developer and co-author of the proposal, put the odds that it comes next at 80% in an interview published on November 4.
Corallo's framing is as notable as the number. He describes the effort as valuable for what it fixes and also for what it would teach: developers who have never shipped a soft fork would get practice, and the community could settle on a reusable method for deploying later upgrades.
No formal timeline exists, and the proposal is far from a rush job. It dates to 2019, and its changes have been deferred for years because none was urgent enough to force action.
For readers new to the term, a soft fork is a change that tightens the rules of the network so that blocks created under the new rules still look valid to nodes that have not upgraded. That backward compatibility makes soft forks the usual way Bitcoin evolves, but it also means the community must be careful, because a change that some participants enforce and others ignore can split the network.
In that sense the decision about the next Bitcoin soft fork is partly a decision about priorities. Every upgrade consumes attention, review time and political capital, and the pool of developers qualified to review consensus changes is small.
2. What does BIP-54 actually fix?
BIP-54 targets four specific vulnerabilities, each of which has been understood by developers for a long time. Its supporters describe it at its core as a fix for problems that most people in the field already agree are problems, which distinguishes it from proposals that add new features and invite debate over whether they are wanted.
The proposal aims to remove what Corallo and others call cruft from the consensus design, meaning accumulated quirks in the rules that make the system harder to reason about and, in some cases, open to abuse. Consensus rules are the shared definitions that every full node uses to decide whether a block is valid, so even small oddities can have outsized consequences.
Corallo told Isabel Foxen Duke, head of the MARA Foundation, that there is a long list of known problems waiting for cleanup. He stressed that the issues are real and could harm Bitcoin, but that they are not emergencies requiring immediate action.
3. How could poison blocks and the time warp attack work?
The first flaw involves so-called poison blocks. A miner could craft a block that takes an unusually long time for other nodes to validate. While competitors are busy checking it, the creator could gain a temporary advantage in building the next block. The weakness is a denial-of-service vector aimed at the mining competition itself.
The second is the time warp. Bitcoin adjusts its mining difficulty every two weeks based on how quickly the previous batch of blocks was found. A loophole in how that window is measured allows a miner holding a majority of the network's hash rate to manipulate timestamps and speed up block issuance, which would bring new coins into circulation faster than intended.
Both attacks require significant resources to carry out, which is part of why they have been tolerated. They are still departures from the behavior the protocol is supposed to guarantee, and removing them would close off options for a well-funded attacker.
None of the four problems has produced a known catastrophe on the live network. That is a reason the fixes have waited, and also a reason supporters say now is a reasonable time to act, while there is no crisis forcing hurried decisions and while the proposal can be examined slowly by many reviewers.
4. Why do Merkle malleability and duplicate coinbase transactions matter?
The third flaw is Merkle malleability. A 64-byte transaction happens to be the same size as an internal node in the Merkle tree, the data structure that summarizes all transactions in a block. In theory, an attacker could exploit that coincidence to forge proofs that trick light clients, which do not download full blocks, into accepting fake transactions.
The fourth concerns duplicate coinbase transactions. Historical quirks in the rules permitted transaction identifiers to repeat, and a duplicate could reappear at a future block height. If that happened, it could overwrite existing coins or disrupt the accounting of the ledger.
Neither scenario is described as imminent. They are examples of the loose ends that accumulate in a system more than a decade old, and fixing them together in one package is the logic behind the cleanup label.
5. Why would the upgrade work as a practice run?
Bitcoin has not activated a soft fork since Taproot, which went live in November 2021. Since then, the network has struggled to agree on further protocol changes, a condition often described as ossification. Proposals such as OP_CAT (BIP-347) and OP_CHECKTEMPLATEVERIFY (BIP-119) have not reached broad consensus.
Corallo says soft forks have always faced technical obstacles, but in recent years political and social friction has become equally significant. A change that is technically sound can still stall if the community cannot agree on how to deploy it or who gets a say in the process.
That is where the practice-run idea comes in. A cleanup that few people oppose gives developers a low-stakes chance to rebuild the habits and procedures that a contested upgrade would later demand.
Ossification is not necessarily a flaw in the eyes of everyone in the community. Many Bitcoin users value a protocol that rarely changes, since stability underpins the network's reputation as sound money. The difficulty arises when the same caution blocks changes that nearly everyone accepts, because it raises the question of whether the system can respond when a real problem emerges.
A cleanup that passes smoothly would be evidence that the process still works. One that stalls would be evidence in the opposite direction, and would be taken seriously by developers weighing how much future risk they are comfortable carrying.
6. What did the Taproot activation debate teach developers?
The Taproot discussion pitted two approaches against each other. One relied on miner signaling thresholds, in which blocks indicate support until enough of them do. The other favored a mandatory flag day, a fixed point when users enforce the new rules whatever miners signal. The argument was long and, at times, tense.
Corallo observed that every recent soft fork has involved significant drama over activation mechanisms. He hopes BIP-54 can work through that process once so that future forks can reuse the result and avoid similar conflict. In his view, a deployment playbook would be a lasting contribution regardless of the specific bugs fixed.
The idea carries a risk: if even a widely accepted cleanup produces a fight over activation, it would show how hard it has become to change the protocol in any way.
Supporters of the cleanup respond that fixes of this kind are a precondition for bigger changes. A protocol with known weaknesses in its difficulty adjustment or block validation is a shakier foundation for new features, and resolving those weaknesses first lowers the risk that a later upgrade interacts badly with them.
7. Who disagrees with the cleanup-first approach?
Paul Sztorc, co-founder and CEO of LayerTwo Labs, posted on X that the prospect of BIP-54 activating is depressing. He called it a janitorial maintenance fork that adds no new functionality, a view shared by people who would rather see the network spend its limited upgrade capacity on features.
Sztorc said he surveyed developers at TABconf in Atlanta and found that most of Bitcoin's most capable developers expect BIP-54 to be the next soft fork. The earliest estimate he heard was September 2027, though most pointed to 2028 or later.
The exchange shows the tension in the debate. Defenders see a necessary, low-controversy step. Critics see an opportunity cost, since a network that can only manage one upgrade every few years has to choose carefully.
8. What comes next for Bitcoin's upgrade process?
No date has been set, and the survey responses suggest that any activation is still at least a year away and probably more. Quantum resistance attracts a great deal of attention, but experts expect a practical cleanup to come first, with the fixes for difficulty adjustment and miner denial-of-service vectors ahead of more ambitious changes.
The more important outcome may be social rather than technical. BIP-54 will test whether Bitcoin can still agree on upgrades, not just whether it can write them. If developers, miners and users can move through a deployment cleanly, the process could serve as a template for later proposals, including ones that are far more contentious.
Readers should watch for any formal discussion of an activation method, since that choice will reveal how much of the Taproot-era disagreement remains unresolved.
Because no schedule exists, the practical advice for users and businesses is simple: nothing needs to be done now. A soft fork of this type would reach ordinary users through routine node software updates, and the long lead time suggests there would be ample public discussion before any activation. Anyone who runs a node or builds software on Bitcoin can follow the proposal in the open, and developers have said little about it that is secret or sudden.