In crypto, governance is the ultimate smart contract. BIP-110 support never cracked 1%—a signal so weak it barely registered on the miner dashboard. Yet the proposal didn't die from a code exploit. It died from a consensus firewall that rejected a parameter change before a single line of implementation code was written.
That firewall is Bitcoin's greatest feature and its most misunderstood vulnerability. As someone who has spent years auditing smart contracts—from DeFi protocols to NFT royalty logic—I've learned that the most dangerous bugs aren't in the execution. They're in the governance process that allows that execution to change. BIP-110 is a case study in why Bitcoin's governance, for all its messiness, remains the industry's gold standard for resistance against arbitrary change.
Context: The Proposal That Never Had a Chance
BIP-110, introduced by Bitcoin Knots contributor Luke Dashjr, aimed to restrict block space used for non-financial data. It proposed limiting OP_RETURN outputs to one year and capping script sizes to reduce what supporters called 'spam'—primarily Ordinals inscriptions and BRC-20 tokens. The technical change was trivial: a soft fork modifying validation rules for certain transaction types. The activation mechanism, however, was radical.
Instead of the traditional 95% miner threshold, BIP-110 proposed User-Activated Soft Fork (UASF) with a 55% miner activation floor. The logic: if even a majority of miners signal support, nodes enforcing the new rules can reject blocks from non-compliant miners, forcing a chain split. Opponents—including Michael Saylor, Adam Back, and Jameson Lopp—immediately flagged the risk. Saylor called it a 'dangerous precedent' that could make valid, fee-paying transactions suddenly invalid. Back bluntly stated the proposal would create a fork, but Bitcoin would not join it.
By early August, miner support hovered at 1%. Node adoption was negligible. The proposal was dead before its deadline. But the autopsy reveals far more than a failed governance experiment.
Core: Forensic Dissection of a Consensus Failure
From a technical standpoint, BIP-110 was never an innovation. It was a parameter adjustment—a patch on a system that had already proved its ability to absorb non-financial data without collapsing. Ordinals transactions, despite their media hype, occupy less than 10% of block space during peak activity. The network's fee market mechanism already prices data: high-value transactions outbid low-value ones. BIP-110 attempted to override that market with protocol-enforced censorship.
Here's where my experience as a smart contract architect kicks in. Code is law, but audit is mercy. In DeFi, I've seen protocols collapse because they underestimated the composability of risk—flash loans exploiting oracle delays, leverage cascading through unguarded pools. Composability is leverage until it becomes liability. Similarly, Bitcoin's block space composability—its ability to carry any data that pays fees—became a liability when a faction decided certain data types were illegitimate.
But the technical risk wasn't in the data. It was in the UASF mechanism. A 55% miner activation threshold is dangerously low. Compare it to the 95% consensus required for most Bitcoin upgrades. That lower threshold lowers the bar for a chain split. Imagine a scenario where 56% of miners signal for BIP-110, and 44% do not. The minority chain, backed by the majority of nodes who reject the change, would continue mining empty blocks or orphan the majority chain's transactions. The result: two Bitcoins, competing for the same ticker, with no clear economic resolution.
Logic dictates value, perception dictates volume. The market correctly priced BIP-110 as irrelevant—bitcoin's price didn't flinch throughout the debate. But the perception that a vocal minority could attempt a UASF with such low support is a vulnerability in itself. It signals that any disgruntled group with enough node operators can attempt to fork the network, even without miner backing.
From an economic perspective, the proposal's supporters claimed it would protect Bitcoin's original vision as a peer-to-peer cash system. But that argument ignores the reality of miner economics. Infinite yield curves break under finite scrutiny. If BIP-110 had passed, miners would have lost fee revenue from Ordinals transactions—a non-trivial percentage in a post-halving environment where transaction fees now account for up to 10-15% of total miner income. The proposal's economic model was backward-looking, trying to preserve a 2013 definition of 'valid transaction' for a 2025 network that had already evolved.
Contrarian: The Blind Spot in the Victory Lap
Most commentators are celebrating BIP-110's failure as a win for Bitcoin's conservatism. I see a different risk. The very fact that a proposal with 1% miner support even made it to the activation deadline reveals a governance structure that is simultaneously robust and fragile.
Robust because the community rejected it without a hard fork. Fragile because the UASF mechanism remains available for any future, better-organized faction. The contract executes, and the architect pays—but when the architect is a decentralized crowd, liability is undefined. If a larger coalition—say, miners and nodes totaling 30%—attempts a UASF with 55% threshold, the chain split probability becomes real. The blind spot is that we treat this failure as a permanent victory, while the underlying tension between data maximalists and payment purists will only intensify as block space becomes more contested.
Furthermore, the Ordinals ecosystem now has a temporary reprieve. But this opposition won't vanish. It will fossilize into more aggressive proposals, possibly hard forks, from the anti-data faction. The irony is that BIP-110's failure may embolden both sides: Ordinals users will continue flooding blocks, and their opponents will look for more extreme measures.
Takeaway: The Next Stress Test Is Already Loading
BIP-110 is dead. But the question it raised—who decides what Bitcoin is for?—will not die. The network's immune system worked this time, rejecting a low-consensus change. Yet every failed attack reveals a potential vector for the next one. As I tell my clients when auditing their protocols: Trust no one, verify everything, build twice. Bitcoin passed this test, but the next stress test—whether economic, regulatory, or governance-driven—is already compiling in the mempool. The only certainty is that the blockchain, like any robust system, will continue to evolve under pressure. The question is whether its governance can adapt without breaking.
