Bitcoin’s Next Fork Gets 80% Odds as Taproot Turns Five
Five years after Taproot, Bitcoin still has not activated another soft fork. Now BIP-54 co-author Matt Corallo puts the odds of the next one at about 80 percent.
A Five-Year Drought, and the Number That Changed It
Five years ago this month, Bitcoin threw a switch and then stopped throwing switches. Taproot, the upgrade that gave the network Schnorr signatures and a cleaner way to hide the conditions under which coins can be spent, activated at block 709,632 on 14 November 2021, after more than 90 percent of miners signaled their support, as CoinDesk reported at the time. Nothing has reached activation since. That makes the run from Taproot to today the longest stretch without a change to Bitcoin’s consensus rules in the network’s history.
On 4 November 2026, that silence finally got a probability attached to it. Speaking on MARA Foundation TV with the foundation’s Isabel Foxen Duke, longtime Bitcoin developer Matt Corallo, a co-author of the proposal most observers treat as the front-runner, said there is roughly an 80 percent chance that the Great Consensus Cleanup, catalogued as BIP-54, will be Bitcoin’s next soft fork, according to a report by Decrypt. He did not attach a date. Developers polled at the TABconf event in Atlanta put the earliest plausible activation in September 2027, with most expecting 2028 or later.
The timing is almost too tidy. Taproot turns five on 14 November, and for most of those five years the live question has not been which upgrade comes next, but whether Bitcoin can still agree on any upgrade at all. An 80 percent estimate from the person who wrote the leading candidate is the most concrete answer the network has had in a long while, even if an estimate is all it is.
It landed in a nervous market. Bitcoin was changing hands near $76,200, down more than 5 percent on the day and well below the all-time high just above $126,000 set in October 2025, according to CoinGecko. Price and protocol run on separate clocks, but the backdrop is worth naming: the people arguing about consensus rules are doing it while holders stare at a drawdown of roughly 40 percent from the peak.
What Matt Corallo Actually Said
Corallo’s framing was pointedly unglamorous. “There’s a laundry list of things we know of that we really need to clean up,” he told Foxen Duke, per Decrypt. “All of these issues are real concerns that could impact Bitcoin negatively, but they’re not like, ‘Oh, the sky is falling.’” The message was that BIP-54 is maintenance, not rescue; the bugs it closes are real, long known, and so far unexploited.
His 80 percent was not a call on price or a prediction that the fork is imminent. It was a bet on sequence: of all the proposals circulating, the cleanup is the one developers are most likely to rally behind first. Corallo described it as “a practical exercise for Bitcoin developers who haven’t yet been through a soft fork,” a way to rebuild a muscle the project has not used in five years.
Not everyone finds the prospect inspiring. Paul Sztorc, co-founder of LayerTwo Labs and a longtime critic of Bitcoin’s upgrade paralysis, called the idea of spending the next fork on housekeeping “depressing,” in the same Decrypt report. The two reactions capture the split running through Bitcoin development in 2026: one camp sees a careful, overdue tidy-up; the other sees a network so stuck that its big comeback is a bug fix.
Why Taproot Is Still the Last Word
To understand why an 80 percent estimate counts as news, look at the drought. Bitcoin shipped consensus changes at a steady clip through its first decade, with Pay-to-Script-Hash in 2012, the BIP66 signature tightening in 2015, CheckLockTimeVerify and CheckSequenceVerify in 2015 and 2016, SegWit in 2017, and then Taproot. SegWit to Taproot took a little over four years. Taproot to now is five and counting, with nothing activated in between.
The one recent attempt showed why. In August 2026, a mandatory-signaling proposal known as BIP-110, aimed at reining in Bitcoin’s growing use as a data-storage layer, reached its signaling block and drew about 2.53 percent support against a 55 percent threshold, according to research by AMINA Bank. A breakaway minority mined a couple of blocks on a separate chain and then stalled. The code worked; the coordination did not.
That is the lesson developers keep circling back to. The hard part of a modern Bitcoin soft fork is not writing the change. It is agreeing on how to turn it on without splitting the network or handing any one group, miners especially, a veto or a trigger it should not have. Five years of failed or abandoned attempts have left the project without a settled answer, and without many people who have run the process from start to finish.
BIP-54 in Plain English: The Cleanup That Goes First
BIP-54 is not new. Matt Corallo first floated a consensus cleanup in 2019; the proposal was revived and carried forward in the years since, largely by developer Antoine Poinsot, picked up its formal BIP number in 2025, and reached a near-complete specification in 2026 that now runs on Bitcoin test networks rather than the main chain. It is catalogued and explained in detail at bip54.org.
What sets it apart from every other proposal in the queue is what it does not do. It adds no new opcodes, enables no new class of application, and changes nothing about how ordinary payments work. It removes what Corallo and others call cruft: a small set of latent bugs that have sat inside Bitcoin’s consensus rules for more than a decade, harmless in practice but dangerous in theory. In his words, it “fixes some stuff that everyone agrees are problems.”
That near-unanimity is the whole point. These are not trade-offs where reasonable developers disagree about fungibility, complexity, or whether Bitcoin should host smart contracts. They are closer to the security hardening every mature system eventually does. They are also a different animal from the application-layer failures that dominated 2026 headlines, such as the signing and key-handling disasters behind the year’s largest exchange losses, which HOGE Wire examined in its account of the $6.3 billion Binance incident. Those were failures of how software and people handle keys. BIP-54 is about the rules every node enforces on every block, a layer no custodian or exchange controls.
The Four Bugs BIP-54 Closes
The cleanup bundles four distinct fixes. None is being actively exploited, which is precisely why they have survived so long; each is a corner case that would only bite under specific, adversarial conditions. The table below summarizes what they are and why they matter.
| Bug | What it is | Worst-case risk | Why it has lingered |
|---|---|---|---|
| Time warp | A loophole in the two-week difficulty retarget that lets a majority-hashrate miner lie about block timestamps | Difficulty collapses, blocks pour out every few seconds, the remaining issuance is drained, and Lightning timelocks break | Known since the early 2010s, never exploited because it needs majority hashrate |
| Long-validation blocks | Legacy, pre-SegWit transactions can demand enormous signature-check work, so a crafted block takes minutes to verify | A miner gains a head start while rivals validate, a denial-of-service lever against the rest of the network | Cheap to ignore until block space and fees made the attack economically plausible |
| 64-byte transactions | A transaction exactly 64 bytes long is the same size as an internal node in a block’s Merkle tree | An attacker can forge a compact proof that fools light wallets into accepting a payment that was never mined | The required work is large but finite, roughly 70 bits, so it stayed theoretical |
| Duplicate coinbase | An old quirk let two coinbase transactions share an identical ID | Coins can be overwritten in the ledger, and a 2010 incident already made about 100 BTC permanently unspendable | A later rule papered over it, but that protection quietly expires around the year 2046 |
BIP-54 addresses each at the consensus layer. It constrains the timestamps on the first and last block of every retarget period to kill the time warp. It caps legacy signature operations per transaction, which trims the worst-case validation time by roughly an order of magnitude. It bans 64-byte transactions outright, closing the fake-proof trick. And it makes Bitcoin’s block-height commitment permanent, so the duplicate-coinbase hole never reopens, as detailed by CoinCentral. Each fix is small; together they close the last widely-agreed holes in rules that have otherwise gone untouched for years.
The Practice-Run Argument
The bugs are the official reason for BIP-54. The strategic reason, the one Corallo kept returning to, is the process itself. “In every recent soft fork, there’s also been a bunch of drama about activation mechanisms,” he said. The fight is rarely about whether a change is good. It is about how the network should say yes.
A low-controversy payload turns that liability into an asset. If almost everyone agrees the cleanup is worth doing, the argument narrows to the one thing Bitcoin genuinely has not resolved: the activation method. Settle it once on a change nobody really opposes, write the result down, and the next upgrade inherits a tested path. “Hopefully we could do a soft fork to go through that drama, and then copy and paste and reuse it and head off some of that drama” for future forks, Corallo told crypto.news.
There is a generational angle underneath this. The developers who steered SegWit and Taproot through activation have largely moved on or stepped back. A large share of the people maintaining Bitcoin today have never shipped a consensus change. The cleanup, on this reading, is partly a training exercise: a way to rebuild institutional memory on a fork where the cost of fumbling the coordination is low, before the network faces one where it is not.
The Activation Machinery Nobody Agrees On
It helps to know what the drama is actually about. Bitcoin has no single, agreed procedure for turning on a soft fork. Over the years it has leaned on variations of a few.
BIP-9 reads miner support from a version bit and activates once a high threshold, historically 95 percent, is met inside a fixed window. Speedy Trial, the mechanism used for Taproot, is a shortened BIP-9 that gives miners a brief window to signal and, if they do, locks the change in. BIP-8 goes the other way: it can force activation at a flag day whether or not miners signal, the approach behind the user-activated soft fork idea that circulated during the SegWit fight.
The disagreement is about legitimacy. Miner signaling is convenient but risks treating hashrate as a vote it was never meant to be, as BIP-110 showed when 2.53 percent support stalled the whole thing. A user-activated flag day sidesteps miners but raises the specter of a chain split if the wider economy does not move together. There is no consensus on which is appropriate for a change that lacks overwhelming, visible agreement. That unresolved question, more than any line of code, is what has kept Bitcoin frozen, and it is exactly what Corallo wants BIP-54 to answer.
Why 80 Percent Is Not a Promise
An estimate from a proposal’s own author deserves a skeptical read, and Corallo left a fifth of the outcome on the table for good reasons. The cleanup is popular in principle, but principle has not been the obstacle; coordination has.
F2Pool, one of the larger mining pools, objected earlier in 2026 to bundling four unrelated fixes into a single change, comparing it to stuffing unrelated measures into one bill, and signaled it would not pre-signal before a formal majority had formed. Sztorc’s “depressing” line points at a different fault line, the camp that would rather see Bitcoin ossify than reopen the activation debate at all, on the theory that every fork is a risk and a frozen protocol is a feature. Between the pools that want cleaner process and the holders who want no process, 20 percent of doubt is not hard to find.
The concrete ways it could slip are easy to list. The activation-mechanism fight could reignite and swallow the cleanup the way it has swallowed others. A meaningful bloc of hashrate could decline to signal. Or the community could decide the scarce attention of its consensus developers belongs on the quantum problem instead, leapfrogging the cleanup entirely. None of these is likely on its own. Stacked together, they are why Corallo said 80 and not 100.
The Queue Behind the Cleanup
BIP-54 is not the only thing waiting. It sits at the front of a line of proposals that range from modest to transformative to unavoidable, and the order in which they move tells you how Bitcoin now thinks about risk. The table below maps the queue as it stood in early November 2026.
| Proposal | What it would do | Status (November 2026) | Realistic timeline |
|---|---|---|---|
| BIP-54, Great Consensus Cleanup | Close four latent consensus bugs, no new features | Specification complete, running on test networks; co-author puts odds near 80 percent | 2027 at the earliest, 2028 or later more likely |
| OP_CTV, BIP-119 | Add simple covenants for vaults and congestion control | Activation client live, signaling window open to 30 March 2027, roughly 0 percent miner signaling against a 90 percent threshold | Stalled, no realistic path this window |
| OP_CSFS, BIP-348 | A covenant primitive often paired with CTV | Proposed, no activation path | Undetermined |
| OP_CAT, BIP-347 | Re-enable data concatenation, unlocking richer, recursive covenants | Specification complete, no activation path, contested | Undetermined |
| BIP-360, post-quantum address type | Add a quantum-resistant way to hold coins | Merged into the proposals repository in February 2026, still a proposal | Multi-year migration once started, estimated near seven years |
Covenant status here is drawn from the comparison maintained by Spark, whose tracker has shown CTV signaling stuck near zero all year. The pattern is clear enough: the boring change is the one with momentum, and everything interesting is either stuck or still a draft.
The Covenant Logjam
The proposals developers are genuinely excited about are covenants, and they are the ones going nowhere. A covenant lets a coin carry rules about how it can be spent in the future, the building block for self-custodial vaults, for cheaper and safer Lightning, and for the bridges that trust-minimized Layer 2 designs depend on. CheckTemplateVerify, or CTV, is the most conservative version, deliberately narrow to reduce the risk of surprises. Even so, its signaling has sat near zero for months.
OP_CAT is the opposite case: a tiny change, just a few lines, that would re-enable an old operation and, combined with Taproot’s signatures, open the door to far more expressive, recursive contracts. That power is also why it is contested, with critics worried about complexity and uses nobody has thought through. Adam Back, the Blockstream chief executive, has gone as far as framing covenant opcodes as a possible “last soft fork” for Bitcoin, arguing the network should pair any such change with heavy formal verification rather than rush it, as CryptoBriefing reported.
This is the backdrop that makes the cleanup-first logic coherent. You do not rehearse a contentious process on your most contentious change. Much of what covenants promise has, in any case, been partly delivered off-chain without waiting for a fork, through the statechains, VTXOs, and asset protocols HOGE Wire traced in its look at Taproot’s dollar rail. The base layer can afford to move slowly on covenants precisely because the second layer has not.
The Deadline That Is Not Optional: Quantum
There is one change Bitcoin cannot defer indefinitely, and it is the deeper reason the practice run matters. In March 2026, research from Google’s quantum team reset the field’s assumptions about how hard it would be to break Bitcoin’s signatures. The work suggested an attack might need under 500,000 physical qubits rather than millions, with a concrete model pointing at roughly 1,200 to 1,450 high-quality logical qubits able to forge a competing transaction in about nine minutes, as CoinDesk reported. Google’s own estimate for useful quantum systems sits around 2029.
Taproot complicates this in one specific way. A Taproot output reveals its full public key on-chain by default, where older address types hid it behind a hash until the coins first moved. That means every Taproot balance is exposed to a future quantum attacker from the moment it is funded, and roughly 6.9 million BTC, about a third of all supply, already sit on exposed-key addresses, per AMINA’s research. A falling market does not change that arithmetic; the key sitting on-chain is exposed whether a coin is worth $76,000 or $126,000.
The answer in progress is BIP-360, a new quantum-resistant address type from developer Hunter Beast that Bitcoin’s reference project merged into its proposals repository in February 2026, as Forbes noted. It is still only a proposal, and co-author Ethan Heilman has estimated it would take about seven years to migrate the network even if work started today. A quantum migration is the hardest fork Bitcoin will ever attempt, touching how every holder secures coins and possibly how dormant balances are handled. No one wants the first fork in six or seven years to also be the scariest one. That, more than the four bugs, is the case for a dress rehearsal.
What Taproot Actually Delivered in Five Years
If the next fork is a rehearsal, it is worth asking how the last one aged. Taproot’s record is mixed, and the gap between its launch pitch and its real-world use is striking. On-chain adoption tells an odd story: Taproot transactions were about 1 percent of the network in early 2023, spiked above 40 percent at the start of 2024 as Ordinals and inscriptions exploded, and have since settled to the mid-teens as that speculative wave cooled into steadier, organic use.
Where Taproot genuinely landed was off the base layer and inside tooling most users never see. Simple Taproot channels became production-ready in Lightning in 2026. Taproot Assets brought dollar stablecoins onto Bitcoin rails, a development that only matters because the dollars riding those rails sit squarely inside the regulatory perimeter the United States finished drawing this year, which HOGE Wire covered in its guide to the 2026 stablecoin rulebook. And the statechain and VTXO wave that now moves value off-chain is built on primitives Taproot introduced.
Where it fell short is just as instructive. Privacy by default, one of the upgrade’s headline promises, never arrived, partly because most wallets and exchanges still hand out older address formats and partly because Ordinals turned the bc1p prefix into the chain’s data-storage address rather than its private one. The sheer unfriendliness of those long addresses is its own adoption drag, a problem HOGE Wire has written about as the 42-character problem. The scorecard below grades the original promises.
| Taproot promise | The 2021 pitch | Verdict at five years |
|---|---|---|
| Schnorr signatures | Smaller, faster, linear signatures | Delivered, shipped in core libraries, in wallets such as Ledger, and across Lightning |
| Key aggregation | Multisignatures that look like a single signature | Partly delivered, live via MuSig2 but mostly in collaborative-custody setups |
| Privacy by default | Complex and simple spends become indistinguishable | Missed, inscriptions made Taproot the data address, not the private one |
| Cheaper complex spends | Only the branch of a contract you use hits the chain | Delivered for those who use the script path |
| Smart contracts and covenants | A foundation for richer on-chain logic | Blocked, still waiting on a fork that has not come |
Why the SEC Is Not in This Conversation
It is worth stating plainly, because the question comes up: no regulator approves or blocks a Bitcoin soft fork. The U.S. Securities and Exchange Commission oversees how coins are offered as securities, how exchanges and custodians operate, and how products such as spot ETFs are structured and sold. It has no lever over how Bitcoin nodes validate a block. A change to consensus rules is decided by the rough agreement of node operators, miners, and developers, not by a rulemaking or a filing.
That is why BIP-54’s fate turns on signaling thresholds and mailing-list debates rather than comment periods. The regulatory action of 2026 happened one layer up, around ETFs, custody, and stablecoins, and it will keep happening there. The irony is that the parts of the Bitcoin stack regulators do touch, the dollar tokens and custodial products built on top, increasingly ride rails that Taproot made possible, even though the rail itself sits entirely outside any regulator’s reach.
What to Watch Between Now and 2027
An 80 percent estimate is a starting gun, not a finish line. A handful of concrete signals will show whether the cleanup is actually moving or quietly joining the pile of stalled proposals.
- A formal BIP-54 activation proposal, with specific block heights and a chosen mechanism, would turn Corallo’s estimate into a live attempt rather than a forecast.
- Miner posture, especially whether pools that objected, F2Pool among them, shift from opposition toward pre-signaling.
- The CTV signaling window timing out on 30 March 2027 with near-zero support, which would confirm the miner-signaling path is exhausted and reopen the user-activated debate.
- Developer gatherings in the TABconf mold, where a rough consensus on activation method could finally form.
- Any named quantum-hardware milestone that shortens the perceived runway for BIP-360 and raises pressure to skip the rehearsal.
- Taproot’s on-chain share, where a durable climb would soften the privacy-missed verdict and a continued drift would harden it.
For now, Bitcoin sits in an unusual place: a network whose defining trait has become how rarely it changes, with its own developers arguing that the cure for that paralysis is to practice changing on something small. Five years after Taproot switched on, the most optimistic thing anyone can say about the next fork is a probability. That it is 80 percent, and not a shrug, is itself the news.
Frequently Asked Questions
What is BIP-54, the Great Consensus Cleanup?
BIP-54 is a proposed Bitcoin soft fork that fixes four long-standing bugs in the network’s consensus rules without adding any new features. It addresses the time warp difficulty exploit, blocks that take too long to validate, a 64-byte transaction trick that can fool light wallets, and an old duplicate-coinbase flaw. First floated by Matt Corallo in 2019, it reached a near-complete specification in 2026 and currently runs only on Bitcoin test networks.
Why has Bitcoin not had a soft fork since Taproot?
Taproot, activated in November 2021, remains Bitcoin’s most recent consensus change, the longest such gap in its history. The obstacle has not been writing code but agreeing on how to activate it. A 2026 attempt called BIP-110 drew only about 2.53 percent miner support against a 55 percent threshold, and the leading covenant proposal, CTV, has sat near zero percent signaling, leaving the network without a settled activation method.
What did Matt Corallo say about an 80 percent chance?
Speaking on MARA Foundation TV on 4 November 2026, Corallo, a BIP-54 co-author, estimated roughly an 80 percent chance that the Great Consensus Cleanup will be Bitcoin’s next soft fork. He described it as a practical exercise for a generation of developers who have never shipped a fork, and a way to settle the activation process once and reuse it for harder upgrades later.
When could BIP-54 actually activate?
There is no formal timeline. Developers polled at the TABconf conference put the earliest plausible activation in September 2027, with most expecting 2028 or later. Activation also depends on resolving which signaling or user-activated mechanism the network will accept, the same disagreement that has stalled other recent proposals.
Does BIP-54 fix Bitcoin’s quantum computing risk?
No. BIP-54 is a consensus cleanup and does nothing about quantum exposure. The quantum fix is a separate proposal, BIP-360, which adds a quantum-resistant address type and was merged into Bitcoin’s proposals repository in February 2026. One of its co-authors estimates a full migration could take about seven years once it begins, which is part of why developers want to rehearse the fork process on the simpler cleanup first.
By Marcus Okafor, senior Bitcoin and layer-1 correspondent at HOGE Wire.