BIP-110's Quiet Death: Why Bitcoin's Data Censorship Fight Was Over Before It Started

On paper, BIP-110 was a technical tweak. In practice, it became a referendum on Bitcoin's soul. The numbers tell the story: as of late July 2025, only 1% of miners signaled support. Node adoption? Negligible. Yet the noise was deafening. Why? Because buried in this failed soft fork is a blueprint of Bitcoin's immune system — and its vulnerabilities. The proposal, championed by Bitcoin Knots maintainer Luke Dashjr, aimed to limit non-financial data embedded in transactions. Specifically, it would cap OP_RETURN output size, restrict script sizes, and ban certain data-heavy script patterns — a direct shot at Ordinals inscriptions and BRC-20 tokens that have flooded blocks since 2023. The activation mechanism was equally contentious: a User Activated Soft Fork with a lowered 55% threshold, bypassing the traditional 95% miner consensus. Context matters here. Bitcoin's block space is a scarce resource paid for through market fees. Ordinals introduced a new class of demand: users willing to pay competitive fees to immortalize JPEGs and arbitrary data. For some, this is innovation; for others, it's spam exploiting a bug in the protocol. BIP-110 was the second generation's attempt to rewrite the rules retroactively. I've spent years auditing smart contracts, and one lesson stands out: parameter changes are never minor. In 2017, I audited a liquidity pool contract that used a Diamond Cut inheritance pattern. The code looked clean, but under specific gas conditions, the reentrancy guard failed. The fix was a single line — but that line changed the entire incentive surface. BIP-110 is that line for Bitcoin. It doesn't change the consensus algorithm; it changes what constitutes a valid transaction. That's a power far beyond a mere fee market adjustment. Let's dissect the core technical mechanics. BIP-110 targets three attack vectors: bloated OP_RETURN outputs (currently limited to 80 bytes, but proposals sought to reduce further), large script data (like those used in Taproot-based inscriptions), and excessive witness data. The intent is to reduce node storage and bandwidth requirements — an ongoing concern as the UTXO set grows. But the execution reveals a flawed assumption: that data utility can be objectively ranked. A transaction paying 1000 sats/vB for a 500-byte inscription is not spam; it's a willing exchange. BIP-110 would invalidate that consent. The week I spent simulating EIP-1559's base fee mechanism taught me this: fee markets are emergent. You cannot design them top-down without unintended consequences. BIP-110 would have shifted fee revenue from data-heavy to plain payment transactions — but at the cost of permissioning block space. The result would be a two-tier Bitcoin: one for 'legitimate' financial transfers and another for 'illegitimate' data. That distinction is political, not technical. Now, the governance layer. BIP-110 died because it couldn't generate enough hashpower signal. At peak, only about 1% of mined blocks indicated readiness. But the UASF threshold of 55% created a dangerous loophole: a well-coordinated minority of node operators could force a chain split. Jameson Lopp warned publicly that this would be 'a recipe for disaster.' He was right. In my post-mortem of the Terra/Luna collapse, I traced how code couldn't fix unsustainable economic assumptions. Here, the unsustainable assumption was that a minority could force a policy change through a lowered activation threshold. The code (UASF) was neutral; the governance was reckless. What made the proposal fail? Three forces aligned. First, miners — who benefit from Ordinals fees (estimated 5-15% of total fee revenue in mid-2025) — had no incentive to restrict their own income. Second, key community leaders like Michael Saylor and Adam Back publicly opposed it. Saylor's argument was philosophical: 'This would overturn a decade of precedent and make certain transactions invalid after they were already considered valid.' Back was more pragmatic: 'If you want to limit data, go fork — but Bitcoin won't follow.' Third, the broader developer community, including Bitcoin Core maintainers, signaled clear disinterest. The proposal's failure was less a defeat than a non-event. But here's the contrarian angle that most analyses miss: BIP-110's failure inadvertently reinforces a governance model that may ossify Bitcoin. By rejecting any change that tampers with transaction validity, the community is effectively sanctifying the status quo. If Ordinals usage continues to grow — potentially consuming 20-30% of block space by 2027 — the fee pressure on ordinary users will intensify. At that point, a more moderate proposal might emerge with genuine miner support. But the precedent set by BIP-110's death could make any future limitation politically toxic. The slippery slope argument works both ways: it not only prevents bad changes but also blocks necessary evolution. Compare this to Ethereum's EIP-4844, which structurally addressed data availability without censoring existing use cases. Bitcoin lacks that flexibility. Its governance is a binary switch: either you allow all fee-paying transactions, or you start picking winners. BIP-110 tried to pick winners — and lost. But the underlying problem won't disappear. Another blind spot: the UASF mechanism itself. While it failed here, a future scenario with a more popular proposal (say, 70% miner support) could see UASF as a counterweight to miner collusion. BIP-110's opponents used UASF's low threshold as a scare tactic, but the concept of user-activated forks has legitimate use cases. By tainting UASF through association with a controversial proposal, the community may have weakened a valid governance tool. Market reaction to BIP-110 was predictably muted. Bitcoin price barely flinched. The CME futures curve showed no term shifts. That's because the market efficiently priced a near-zero probability of passage. What matters is the latent signal: the debate exposed a deep ideological rift between Bitcoin's 'pure money' faction and its 'settlement layer for everything' faction. This rift will not heal. It will widen with each new ordinal and each fee spike. Gas isn't the only resource that matters; block space carries a hidden governance tax. Every transaction consumes not just bytes but also community attention. BIP-110 was a failed attempt to reset that tax. Smart contracts aren't the only things that can be reentered; governance can be too. The same arguments will recur. I see three signals worth monitoring. First, the proportion of block space used by data-heavy transactions. If it crosses 15% consistently, expect renewed pressure. Second, the growth of Bitcoin Knots as a client. If its share of reachable nodes exceeds 5%, it signals a viable alternative for dissent. Third, public statements from large mining pools. A single pool switching its stance could revive the proposal, though unlikely. My takeaway is simple: BIP-110's death is not a victory but a reprieve. The underlying tension between neutrality and efficiency will continue to test Bitcoin's governance. The protocol's strength lies in its inertia — but inertia can become rigidity. The next halving cycle, with reduced block subsidies and higher fee reliance, will force a reckoning. Until then, Ordinals keep minting, nodes keep syncing, and Bitcoin's governance remains its greatest strength and its most fragile fault line. This fight isn't over. It's just paused.