BIP-110 Explained: Why “Spam Controls” Could Reshape Bitcoin Governance

Bitcoin is again debating where its protocol guardrails should sit. The flashpoint is BIP-110, a soft-fork proposal that would curtail several ways to embed arbitrary, non-financial data on-chain. The split isn’t really about JPEGs or token tickers. It’s about precedent: whether Bitcoin should use consensus rules to police content, even temporarily.

What BIP-110 actually changes - Most new transaction outputs limited to 34 bytes - OP_RETURN restored to an 83-byte ceiling - Certain witness elements capped at 256 bytes - Temporary curbs on Taproot features heavily used for inscriptions

Backers argue this trims blockchain “spam,” preserving Bitcoin’s monetary focus. Opponents counter that these are currently valid, fee-paying transactions; changing consensus to exclude them crosses a line and risks a chain split. The proposal’s mandatory signaling window opens in August, and miner support hovers near 1% on public dashboards—an important data point when evaluating activation safety.

Why precedent—not pictures—matters The code path here isn’t about aesthetics; it’s governance. Once consensus rules are used to filter transaction types judged “undesirable,” even for a limited time, the protocol stops being purely neutral about payloads and starts expressing policy. That shift reverberates.

- Technologically, consensus-level rejections are binary: nodes either accept or orphan blocks. There’s no graceful degradation. That brittleness raises the chance of accidental forks, particularly when rules touch Taproot or witness semantics that wallets and services interpret differently. - Psychologically, Bitcoin’s social contract has emphasized predictability and permissionlessness. Jameson Lopp has warned that changing the rules to screen out certain uses undermines those expectations. Trust in ossification is path-dependent; once bent, it’s easier to bend again. - Commercially, fee markets are messy by design. Ordinals and BRC-20s drove block space demand, lifting miner revenue and, by some estimates, reinforcing long-run security. Reclassifying that demand as “spam” swaps a market outcome for a policy call—one that could chill developer roadmaps and enterprise integrations tied to Taproot features. - Ethically, content-neutral settlement is a core claim of public blockchains. Michael Saylor has argued that there are far more pressing threats than inscriptions, and that invalidating valid transactions to win a spam fight sets the wrong bar for future changes.

The power centers are talking—loudly Luke Dashjr and others view inscriptions as an abuse of block space. Adam Back has emphasized that Bitcoin’s decentralization makes it hard to impose preferences; those who disagree can coordinate a fork, but “Bitcoin won’t be joining it.” Samson Mow has urged treating participants as an alliance with different roles. He opposes BIP-110 despite sharing spam concerns, and criticized recent OP_RETURN policy handling—citing bans on GitHub contributors and hasty approvals—as avoidable unforced errors that inflamed users.

How we got here Ordinals, introduced in early 2023 by Casey Rodarmor, leveraged SegWit and Taproot to bind images, text, and other data to individual satoshis. The result was NFT-like assets on Bitcoin, a surge in block space demand, and higher fees. Supporters pointed to strengthened miner economics; critics labeled the activity extraneous to Bitcoin’s monetary mission.

The governance frame that matters now Bitcoin’s history is informative. During the Blocksize Wars (2015–2017), the network rejected larger base-layer blocks, while dissenters forked to create Bitcoin Cash in 2017 and later Bitcoin SV in 2018. The lesson wasn’t that Bitcoin never changes—it’s that changes surviving contact with the network tend to be conservative, broadly signaled, and backed by clear economic majorities.

BIP-110 arrives with low miner signaling and direct impacts on currently valid transactions. That combination elevates fork risk and reputational risk. If the real objective is curbing resource abuse without eroding neutrality, the safer toolkit sits at the policy layer—relay rules, fee differentials, standardness—while preserving consensus as the last resort. Use markets to price block space; use consensus to defend safety and liveness.

The debate will keep circling back to this: once you encode taste into consensus, it’s hard to claim neutrality the next time a new use case stresses block space.