.jpg)
Bitcoin cannot activate any soft forks for the foreseeable future. That is not a critic's jab; it is the assessment of Paul Sztorc, the Drivechain creator and LayerTwo Labs CEO, after BIP-110, the anti-spam temporary soft fork, collapsed with 2.53% miner support and its enforcing branch died two blocks after splitting from the network. All soft forks since Taproot have failed to activate, and this was no exception, he told reporters. Coming from the man whose BIP 300 sidechain proposal needs exactly the consensus change Bitcoin can no longer deliver, the diagnosis reads as an insider's eulogy for Bitcoin's upgrade machinery.
How the BIP-110 Failure Proved the Point
The numbers from BIP-110 are the evidence. The proposal, formally the Reduced Data Temporary Softfork, sought seven consensus restrictions lasting roughly a year, including an 83-byte cap on OP_RETURN outputs and a 256-byte limit on certain data pushes, aimed at curbing the inscription-linked data storage that has pushed Bitcoin's transaction counts to historic highs. Its voluntary activation window required 55% of blocks to signal support. It got 51 supporting blocks in a 2,016-block difficulty period, 2.53%. By August 2 the target was mathematically unreachable, with 28 of the first 1,108 blocks signaling. The enforcing fork then split at block 961,632 on August 8, produced two blocks, and stalled permanently, inheriting Bitcoin's mining difficulty of 127.48 trillion with roughly 257 petahashes per second assigned to it. Strategy's Michael Saylor estimated 99.85% of hash power stayed with the dominant chain. The minority branch could not even reach its difficulty adjustment. It was a schism without a congregation.
The defeat was comprehensive enough to cover both ideological sides of the argument: Bitcoin Knots maintainer Luke Dashjr wanted the data restrictions to keep Bitcoin monetary; Saylor and Adam Back warned the rules would break Bitcoin's neutrality by rejecting structures the network currently accepts. Neither side won. The mechanism lost.
Not Even OP_CAT Can Pass
The frozen upgrade pipeline extends far past one contested proposal. Taproot activated November 14, 2021 at block 709,632 through the Speedy Trial process, introducing Schnorr signatures without splitting the network. Since then: nothing. Sztorc's sharpest example is OP_CAT, a 13-line opcode that existed in Bitcoin's original software before Satoshi disabled it in 2010 over security concerns, with a modern proposal to restore it for covenants, vaults and programmable spending conditions. If a 13-line change with developer enthusiasm and a Satoshi pedigree cannot activate, the barrier is not the proposal, it is the process. BIP-360, the post-quantum address proposal, faces the same wall: a genuinely urgent use case, no activation path.
The mechanism failure has consequences beyond features. Bitcoin's consensus rules are now effectively frozen not by design but by deadlock, and the network is running the experiment of whether absolute immutability at the base layer is a strength or a slow-motion rot. The honest answer is that nobody knows, and both readings are sincerely held.
Why Drivechains Need the Deadlocked Thing
Here is the irony at the center of Sztorc's position: BIP 300 would let developers test experimental rules on opt-in sidechains with a two-way peg, exactly the escape valve a frozen base layer needs, and BIP 300 is itself a soft fork. Asked how it could overcome the resistance that killed BIP-110, Sztorc was direct: It cannot. Each Drivechain will have its own brand, same as Liquid, Lightning, he said of fragmentation concerns, comparing the trust model to the sidechain and second-layer rails whose own history includes episodes like the Liquid Network's $3,400 BTC recovery saga. Drivechains also carry their own security dispute: BIP 300 assigns miners the role of approving sidechain withdrawals through block voting, and critics argue miners could coordinate to approve an invalid withdrawal. Sztorc's defense is economic: if the chain is popular, it will generate fees for miners, and if that revenue is large relative to the coins in the peg, attacking it destroys the income stream.
That security model asks users to trust the incentive math rather than the cryptography, the same trade Liquid and Lightning make in different forms, and it now asks for the one thing the network has stopped granting: a consensus change.
What This Means for Bitcoin's Roadmap
The practical takeaway for holders: replay-protection risk from BIP-110, which developer Kevin Loaec warned could copy transactions across branches, is moot now that the minority chain is dead, but the next attempt at any fork will revive it. Watch whether a future proposal tries the user-activated route instead of miner signaling, because BIP-110's enforcing-node tactic, plus the prepared proof-of-work change code developer Chris Guida described, showed what a determined minority can attempt. Watch whether Foundry's pre-vote customer polling on signaling becomes a governance norm, which would formalize what is currently an informal veto, and remember that the loudest institutional voice in the debate was Strategy, whose 845,050-BTC treasury now pauses and resumes with the market. And recognize what Sztorc's diagnosis means: for now, Bitcoin's only upgrades are software, not consensus. The network that once shipped SegWit and Taproot is, by its own participants' account, done changing its rules, possibly forever, or at least until a crisis strong enough to reopen the question. That is either Bitcoin's greatest feature or its biggest unfinished argument, and the market has decided not to wait on the answer.
