Censorship or Consensus? Why BIP-110's Collapse Defends Bitcoin's Neutral Blockspace

The near-total failure of the "Reduced Data Temporary Soft Fork" to attract miner or node support reinforces a core economic principle of the world's most secure blockchain: on Bitcoin, blockspace is a neutral, free market, and any fee-paying transaction is a valid one.

 

Bitcoin's most consequential governance battles rarely play out in public view, but a high-profile ideological rift has pushed the network's foundational architecture to a crossroads. BIP-110, formally titled the "Reduced Data Temporary Soft Fork," is a controversial Bitcoin Improvement Proposal designed to filter and restrict non-monetary transaction data at the consensus layer. As the network heads toward a mandatory activation window in early August 2026, the proposal has run into a wall of resistance from Bitcoin's most influential institutional and technical figures.

The proposal which originally surfaced as BIP-444 in late 2025 before being renumbered aims to implement a temporary, one-year soft fork that would modify Bitcoin's consensus rules to curb data-embedding practices, specifically targeting the transaction activity that critics label "spam" generated by Ordinals, Inscriptions, BRC-20 tokens, and Runes. Yet as the projected September 1, 2026, activation date approaches, the technical and economic reality for BIP-110 is stark. Miner signaling has hovered near zero, sitting below 1% and frequently registering at 0.00% of recent blocks, while node adoption has stalled in the low single digits at roughly 2.4% of listening nodes. With no major mining pool behind it, the proposal is on track to fail to achieve network-wide consensus, and at most could spawn a small minority chain rather than change Bitcoin itself.

 

 

 

The push for consensus-level data caps suffered a decisive blow when senior industry leaders publicly rejected the protocol change, aligning the network's largest corporate balance sheet with its premier cypherpunk technical lineage. Michael Saylor, executive chairman of Strategy (formerly MicroStrategy), took a blunt economic stance, arguing that the greater threat to Bitcoin was not spam itself, but the precedent of a consensus change that could invalidate transactions that are valid and fee-paying today. He urged the community to focus its energy on more pressing issues. "There are 110 things more dangerous to Bitcoin than spam," Saylor wrote on X, framing the proposal as a self-inflicted risk that converts a localized fee dispute into a heavy-handed protocol intervention that would undermine the predictability institutional allocators require before committing billions of dollars to the asset.

Adam Back, the Blockstream co-founder whose hashcash design is cited in the Bitcoin white paper, attacked the proposal from an architectural perspective, calling it a reckless attempt to enforce subjective behavioral constraints through the consensus layer. Back argued that decentralization explicitly prevents any single faction from dictating how others use the open network, and he offered the proposal's backers many of whom he characterized as well-meaning relative newcomers; a stark ultimatum. Bitcoin "respectfully says no," he wrote, adding that the minority's legitimate, permissionless recourse is to group together and fork away, but that Bitcoin itself "won't be joining it." In a separate assessment, Back described the proposal as breaking multiple things without stopping the embedding it targets, calling each individual flaw fatal on its own.

BIP-110's underlying mechanics have faced severe criticism from veteran Bitcoin developers. Rather than following the traditional standard that requires an overwhelming 95% miner-signaling threshold to safely lock in an upgrade, the proposal deploys a User-Activated Soft Fork (UASF) with a lowered 55% early-lock-in threshold, backed by a mandatory signaling window near block 961,632 projected for around August 7, 2026 that would force enforcing nodes to reject any block failing to signal support regardless of whether miners agree.

At the consensus level, the proposal introduces seven restrictions. In summary, it caps most new transaction outputs at 34 bytes; restores the long-standing 83-byte policy limit on OP_RETURN outputs as a consensus rule; limits individual data pushes and witness elements to 256 bytes; invalidates all methods of embedding contiguous arbitrary data larger than 256 bytes; restricts large scriptPubKey and Tapleaf formats that are used almost exclusively for data embedding; restricts Taproot annexes and oversized control blocks; and permits only well-defined witness versions to be spent during the deployment period, temporarily disabling certain opcodes and upgrade hooks. Crucially, the rules are designed to auto-expire roughly one year after activation, and inputs spending UTXOs created before activation are permanently exempt.

The danger applies only to a specific edge case: a pre-signed transaction spending a Taproot (P2TR) output created after activation, which must be both confirmed and spent during the one-year deployment window, and which selects a tapleaf that violates the new rules. Existing funds and any UTXO created before activation are unaffected, and there is no deadline to move them. Developer Jameson Lopp, who published one of the most detailed critiques calling the proposal reckless and doomed to fail, has centered his objection on this compatibility burden alongside the far larger risk of a chain split, arguing that forcing a contentious change through a 55% UASF greatly increases the odds of two competing chains each claiming to be the real Bitcoin.

Beyond the freeze-risk debate, two structural hazards have drawn the sharpest technical fire. The first is a centralization vector: capping the public peer-to-peer relay network does not actually stop high-volume data protocols, but instead pressures data-heavy issuers to bypass the public mempool and deal directly with large mining pools to get their transactions confirmed. That dynamic risks stripping fee revenue away from standard decentralized miners and concentrating a private blockspace market in the hands of a few industrial operators. The second is inherent circumvention. Security researcher Peter Todd demonstrated the futility of the change by embedding the entire text of the BIP-110 proposal on-chain inside a single transaction that fully complied with the proposal's own rules

The proposal's provenance has added a further layer of controversy. BIP-110 is credited to the pseudonymous developer Dathon Ohm, with longtime data-limit advocate Luke Dashjr associated with the original draft, but the authorship is disputed. Bitcoin Core developer Greg Maxwell has alleged that mining firm Ocean Mining was the true author and would present it under cover of a pseudonym, a claim Dathon Ohm denies. Even Bitcoin's own process reflected the skepticism: BIP editor Mark "Murch" Erhardt assigned the proposal its number while openly describing it as a misguided and unusually careless soft-fork proposal, publishing it only because it met the repository's procedural criteria rather than as any endorsement of its merits.

The lopsided metrics surrounding the proposal confirm that the broader ecosystem views a consensus-level intervention as a far greater risk than tolerating periodic high transaction fees. On the activation side, mainchain Bitcoin operates on strict miner-hashpower enforcement thresholds and a pure free-market transaction philosophy in which any transaction that pays its fee is valid; BIP-110, by contrast, relies on a contentious 55% UASF and a subjective filtering standard that screens out bytes deemed non-monetary. On support, the contrast is even starker. The overwhelming majority of miners have declined to signal for the change, leaving BIP-110 signaling near zero, and node adoption has plateaued in the low single digits.

That miner silence is not purely ideological. Ordinals and Runes activity generates real, fee-paying demand that has become a meaningful slice of miner revenue, and fee swings feed directly into mining profitability, so any rule that removes fee-paying transactions works against miners' rational self-interest. In this sense, Bitcoin's incentive structure did much of the work in stopping the proposal. There is also a tooling dimension: by restricting Taproot tree sizes and certain script constructions, the filter would constrain advanced use cases such as complex covenants and Layer-2 scaling designs, whereas the unrestricted protocol continues to support that innovation surface.

The structural defeat of BIP-110 is a validation of Bitcoin's institutional maturity. Where a puritanical faction viewed the proposal as routine maintenance to flush out junk data, the broader market read it as an unacceptable censorship vector and a dangerous precedent. By declining the soft fork, the network has reaffirmed its core economic covenant: blockspace is a neutral ledger, and validity is determined by fees paid rather than by the social acceptability of a transaction's contents. Bitcoin's multi-trillion-dollar utility rests on predictable, uncompromising rules. Mempool congestion and elevated fees can be inconvenient, but rewriting the consensus rulebook to selectively permit or reject transaction types is the kind of change the network's governance is deliberately built to resist.

 

What is BIP-110? BIP-110, the "Reduced Data Temporary Soft Fork," is a proposed Bitcoin soft fork that would add seven consensus rules limiting the amount of arbitrary, non-monetary data a transaction can carry. It targets Ordinals inscriptions, BRC-20 tokens, Runes, and oversized OP_RETURN payloads. It originally surfaced as BIP-444 before being renumbered.

When does BIP-110 activate, and will it pass? The proposal has a mandatory signaling window near block 961,632, projected for around August 7, 2026, with activation projected near September 1, 2026, and the rules set to auto-expire about a year later. However, with miner signaling below 1% and node adoption around 2.4%, it is widely expected to fail to achieve network-wide consensus and, at most, produce a small minority chain.

Why do Michael Saylor and Adam Back oppose BIP-110? Saylor argues the real danger is the precedent of a consensus change that could invalidate currently valid, fee-paying transactions, not spam itself. Adam Back argues the proposal breaks multiple things without stopping the data embedding it targets, and that using a low-threshold UASF to force a contentious change violates the principle that no single faction should dictate how others use the network.

What is a User-Activated Soft Fork (UASF)? A UASF is an activation mechanism in which nodes enforce new consensus rules regardless of whether miners signal support. BIP-110 uses a modified path requiring only 55% miner signaling for early lock-in, plus a mandatory flag-day fallback; far below the traditional 95% miner threshold, which critics say reveals its lack of broad support and raises chain-split risk.

Does BIP-110 put existing Bitcoin at risk of being frozen? For the vast majority of holders, no. UTXOs created before activation are permanently exempt, and there is no deadline to move funds. The narrow freeze risk applies only to a specific edge case involving post-activation Taproot outputs in pre-signed transactions that must be confirmed and spent during the one-year window using a tapleaf that violates the new rules.

Can BIP-110 actually stop data spam? Critics say no. Peter Todd embedded the full text of the BIP-110 proposal on-chain in a single transaction that complied with the proposal's own rules, demonstrating that determined actors can route around the restrictions. The proposal's own specification concedes it raises the cost of data storage rather than eliminating it.

Who wrote BIP-110? Authorship is disputed. It is credited to the pseudonymous developer Dathon Ohm, with Luke Dashjr associated with the original draft. Greg Maxwell has alleged that mining firm Ocean Mining was the true author, a claim Dathon Ohm denies.

What does BIP-110's failure mean for Bitcoin's governance? It demonstrates that Bitcoin resists rushed or narrow consensus changes even when a vocal faction supports them, because activation ultimately depends on thousands of independent miners and node operators each opting in. For institutions, this reinforces the network's core adoption case: governance may be slow and contested, but that same friction protects the predictability and neutrality the network's value depends on.