The BIP-110 Fork: A Failure Foretold – Anatomy of a Consensusless UASF
Eight hours. Two blocks. A graveyard shift that ended before midnight. On August 9, 2024, Bitcoin’s BIP-110 fork launched with the quiet confidence of a software update – and died with the thud of a ghost chain. The numbers tell the story: at block height 961,632, nodes running the BIP-110 client began rejecting blocks that did not signal support for the proposal. By height 961,633, only two blocks had been mined on the new chain. The main chain, meanwhile, had already reached 961,681. The fork was not a schism; it was a hiccup. Within minutes, it became clear that the entire exercise was a simulation of governance without consent.
This is not a story about a technical flaw. It is a story about the illusion of consensus in Bitcoin’s protocol layer. The BIP-110 proposal aimed to restrict non-financial data writes to Bitcoin’s block space – specifically targeting Ordinals inscriptions, BRC-20 tokens, and other data-heavy use cases that had proliferated since the 2023 Ordinals revival. The mechanism was a user-activated soft fork (UASF): nodes would enforce a new rule at a predetermined time, regardless of miner signaling. The idea was to “cleanse” Bitcoin’s block space, returning it to a pure monetary network. But the execution was a textbook case of code-as-law overreach.
“Beneath the yield lies the rot.” The rot here was not in the code – it was in the assumption that code alone could override economic reality. The BIP-110 activation threshold required 55% miner signaling support within a difficulty adjustment period. In the previous cycle, only 51 of 2,016 blocks (2.53%) had signaled support. The gap was not a margin; it was a chasm. Yet the developers chose to flip the switch anyway, triggering a UASF that forced nodes to reject blocks from miners who had not opted in. The result was a chain that produced two blocks in eight hours – a hashrate share of roughly 4% of the network’s expected output. For context, a stable chain requires at least 50% of the network’s hashrate to avoid frequent reorganizations. At 4%, the fork was a sitting duck for double-spend attacks, griefing, and eventual abandonment.
From my experience auditing 45 whitepapers during the 2017 ICO craze, I learned that hype is noise; structure is signal. The BIP-110 fork lacked structural integrity from the start. The proposal was not a novel consensus mechanism – it was a parameter tweak wrapped in an ideological flag. The core change was simple: nodes would reject any transaction that included non-financial data (e.g., inscriptions, metadata, or references to external data). This was not a scalability upgrade, nor a security patch. It was a policy decision enforced at the protocol level. But Bitcoin’s governance is not a democracy of nodes; it is a trilemma of miners, developers, and users. Miners, who control the hashrate, have the final say. And they voted with their hashpower: they ignored the fork.
Why did miners reject BIP-110? The answer lies in the tokenomics. Ordinals inscriptions had become a significant source of fee revenue for miners. By mid-2024, inscription-related fees accounted for an estimated 15-20% of total transaction fees on the Bitcoin network. For small to mid-sized mining pools, this was a meaningful supplement to the block subsidy. BIP-110 would have eliminated this revenue stream entirely. The proposal was, in effect, a tax on miners’ income, imposed by a faction of developers who believed that Bitcoin should be a “pure” monetary network. Miners, being rational economic actors, refused to cooperate. “Beauty is the mask; geometry is the bone.” The aesthetic of a clean, data-free blockchain was beautiful to some, but the geometric reality of miner incentives made it impossible.
The failure of BIP-110 is not an isolated incident. It is the latest chapter in a long history of Bitcoin governance battles: the blocksize war (BCH 2017), the SegWit2x debacle, the Taproot activation (which succeeded, but only after months of consensus-building). Each time, the lesson has been the same: protocol changes require broad support from miners, exchanges, and the user community. BIP-110 attempted to bypass this by using a UASF – a tool that was originally designed for emergency scenarios (e.g., to force activation of a widely supported upgrade that was being blocked by a minority). Here, the UASF was used to force an upgrade that had less than 3% miner support. That is not a soft fork; it is a hostile takeover attempt.
Let me be clear: I do not follow the wave; I measure its depth. The depth of support for BIP-110 was negligible. The proposal’s failure was not just predictable – it was mathematically certain. Yet the event reveals deeper truths about Bitcoin’s ecosystem.
First, the fork’s rapid death confirms that Bitcoin’s governance is resilient against unilateral action. The “code is law” philosophy works only when the code is backed by sufficient economic weight. Here, the code ran on a handful of nodes, while the rest of the network simply ignored it. The main chain never paused; it continued producing blocks every 10 minutes. The fork was a ghost that faded before dawn.
Second, the incident highlights the growing divide between Bitcoin’s “maximalist” purists and the pragmatic, revenue-seeking miners. The purists see Ordinals as spam that clogs the network and undermines Bitcoin’s digital gold narrative. The miners see them as a legitimate source of income. This tension will not disappear. Future proposals that attempt to restrict data usage – such as BIP-119 (CTV) or OP_CAT – may face similar resistance if they threaten miner revenue. But there is a contrarian angle: the BIP-110 failure might actually strengthen the case for non-financial use cases. By proving that the protocol cannot be changed without miner consent, the event has given Ordinals and BRC-20 tokens a “safe harbor” – at least for the medium term. The risk of a protocol-level ban has been eliminated. The market will price this in.
Third, the fork’s collapse has implications for the broader crypto ecosystem. DeFi and NFT participants on Ethereum, Solana, and other chains should take note: Bitcoin’s governance is not a monolith. It is a messy, multi-stakeholder negotiation that can be gamed, but not easily hijacked. The BIP-110 episode is a reminder that the most secure chain is not the one with the most elegant code, but the one with the most aligned incentives.
From a regulatory perspective, the BIP-110 failure is a non-event. The US SEC has not yet taken a definitive stance on Ordinals, and a protocol-level ban would have made the question moot. Now, the regulatory uncertainty remains. But the market has already moved on: ORDI and other BRC-20 tokens saw a modest rally in the days following the fork’s death, as traders priced in the reduced tail risk.
What about the risk of future attacks? The fork chain, with only two blocks, is virtually nonexistent. But there is a non-zero probability that a small group of miners could continue to produce blocks on the fork, creating a “zombie chain” that periodically appears to challenge the narrative. This is unlikely, but it would be a persistent nuisance. The more immediate risk is that the BIP-110 supporters – embittered by their failure – could pivot to other tactics, such as pushing for miner-imposed transaction filtering at the software level (e.g., via custom mining templates). This would be a subtle, non-protocol way to achieve the same goal. But it would require coordination among major mining pools, which is unlikely given the current fee incentive.
Silence is the loudest indicator of risk. In the days after the fork, the silence from the BIP-110 camp was deafening. No post-mortem, no apology, no plans for a revised proposal. This suggests that the proponents were either caught off guard by the failure or had no fallback strategy. Either way, the credibility of the group has been damaged. It will be years before another UASF of this nature is attempted.
For the average Bitcoin holder, the event is a blip. Your BTC on the main chain is safe. Do not touch the fork chain tokens – they are worthless except as a historical curiosity. For developers and governance watchers, the event is a case study in the limits of code-based activism. And for the Ordinals community, it is a victory – but a temporary one. The ideological battle is not over; it has merely shifted to a different arena.
“Hype is noise; structure is signal.” The structure of Bitcoin’s governance has spoken: unilateral changes without miner support will fail. The BIP-110 fork is now a footnote in Bitcoin’s history. But the lessons it teaches – about incentives, about consensus, about the futility of ignoring economic reality – will echo for years to come.
As I finish this analysis, I recall a quiet afternoon in Vienna, 2021, when I was examining the solvency proofs of a collapsed lending platform. The data was cold, but it told a clear story. The BIP-110 story is equally cold. The code did not lie; the governance did. The fork was dead before it was born. The only question now is: will the next proposal learn from this failure, or will it repeat the same mistake with a different mask?
The answer, I suspect, lies in the geometry of incentives. Beauty fades. Bone remains.
