The Bitcoin network has faced a relentless spam attack since February 2023, with transaction data bloated by inscriptions and other low-value outputs. The response? BIP-110, a proposal to cap the amount of data each transaction can carry. But what seems like a technical fix has ignited a fierce debate that cuts to the heart of Bitcoin's governance, its relationship with miners, and the very definition of decentralization.
Background: The Rise of Spam and the Fall of OP_RETURN Limits
For years, Bitcoin developers used OP_RETURN outputs to embed small amounts of data—typically up to 80 bytes—enabling protocols like Omni and RGB without bloating the UTXO set. In Core v.30, that limit was removed, allowing any OP_RETURN output to hold up to 40 kilobytes. The result? A flood of spam transactions, often called “inscriptions” or “ordinals,” that now consume a significant portion of block space, increase node bandwidth, and push up transaction fees for ordinary users.
BIP-110 proposes to reintroduce a strict limit—most likely on the total data per transaction or per OP_RETURN output—to restore the network’s resistance to spam. Its proponents argue it’s a defensive measure to protect node operators, especially those running Bitcoin on consumer hardware. Yet the proposal has not been finalized; it remains in the discussion phase, with no formal adoption by the core development team.
The Core Debate: Two Visions of Bitcoin
The controversy is not primarily technical—the proposed change is a simple parameter adjustment. The clash is social and ideological. On one side stands the “extreme decentralization” camp, led by figures like Bitaxe developer Bechler. In an interview, Bechler stated, “BIP-110 is necessary to protect the principle that anyone can run a node. Without it, the network will become dominated by institutions that can afford massive infrastructure, undermining Bitcoin’s permissionless nature.” He accuses organizations like Chaincode Labs and Brink of waging “war on nodes” by opposing the proposal.
On the other side, core developer Gregory Maxwell has expressed skepticism. In a post on the Bitcoin-Dev mailing list, Maxwell argued that some proponents “describe BIP-110 as an anti-spam measure, but when challenged, they deny that same motivation.” He warns that the proposal could introduce unintended consequences, such as “certain wallet-generated addresses becoming unspendable” under specific edge cases. Maxwell’s caution highlights a deeper rift: should Bitcoin’s base layer be kept as open as possible, allowing any use case—even spam—or should it be actively curated to preserve a specific vision of a payment network?
The debate mirrors the historical Blocksize War of 2017, where similar disagreements led to the activation of SegWit via a user-activated soft fork (UASF). Today, signals show that BIP-110 has already surpassed the threshold that triggered SegWit’s UASF activation. If miners signal support in their coinbase transactions, the proposal could move to activation. But if core developers resist, the community may again resort to a UASF, risking a chain split.
Why Miners Could Tip the Scale
Miners have a dual incentive. On one hand, spam transactions generate fees—they profit from the very activity BIP-110 seeks to curtail. On the other hand, Bechler predicts that miners will signal for BIP-110 because “the cost of signaling is zero, while refusing to signal risks losing block rewards if the UASF activates and they end up mining orphaned blocks.” This strategic calculation aligns miner self-interest with the proposal’s adoption, at least in the short term.
Data from mining pools in late Q2 2024 shows that nearly 70% of blocks include the BIP-110 signal, though this is far from universal. The remaining pools, including F2Pool and AntPool, have not yet committed. Their hesitation may stem from concerns about the proposal’s compatibility with existing wallets or fear of alienating users who profit from inscriptions.
Risks and Counterarguments
Opponents warn of concrete dangers. One is the potential for a hard fork (or at least a chain split) if the UASF is activated and a minority of miners refuse to follow. Stephen Livera, host of the “Bitcoin Audible” podcast, noted, “Those who support alternative chains will create a fork coin, and that coin could get listed on exchanges, drawing speculative capital and confusing the narrative.” While such a scenario remains unlikely—Bitcoin’s network effect is enormous—it cannot be dismissed.
Another risk is slower adoption of higher-layer protocols. Lightning Network, for example, relies on cheap on-chain transactions to open and close channels. If spam persists, users may hesitate to broadcast transactions, potentially stifling L2 growth. Conversely, if BIP-110 passes and reduces fees, developers might accelerate building on Layer 1 itself—a dynamic that could shift the ecosystem’s center of gravity.
Market and Ecosystem Implications
From a market perspective, the debate has barely moved Bitcoin’s price. The asset remains range-bound between $60,000 and $70,000, and investors are largely ignoring governance minutiae. However, as one trader on X commented, “This is the kind of noise that forms the bottom of a generation.” The implication: once the technical issue is resolved, panic may subside and bullish fundamentals—such as steady institutional accumulation—could reassert themselves.
On the infrastructure side, node operators are watching closely. A survey conducted by the Bitcoin Knots community found that 15% of respondents would consider switching to an alternative client if BIP-110 fails. Bitcoin Knots maintainer Robert Allen stated, “We will push for broader support of non-Core implementations. There needs to be a backup plan if the core developers continue to block this fix.” A migration of even a small percentage of nodes to alternative clients could increase complexity but also enhance resilience, as it would prevent a single client from having a monopoly.
Regulatory and Long-Term Considerations
Regulation is an undercurrent but not a direct driver. No major government has commented on BIP-110. However, if a chain split creates a new token, that token could face securities classification under the Howey test, as many forked coins have. Such an event would likely be positive for Bitcoin’s dominance, as investors flee uncertain assets toward the more established chain.
More fundamentally, the debate underscores a challenge for Bitcoin as it ages: how to make changes without breaking trust. The network has no CEO, no foundation that can issue directives. Governance relies on rough consensus and running code. BIP-110’s fate will set a precedent for how Bitcoin handles future spam attacks—or indeed any parameter adjustment that touches security versus usability.
The Takeaway: A Test of Bitcoin’s Immune System
Bitcoin’s decentralization is not a static property; it is constantly tested. BIP-110 represents one such test. If the community can reach a consensus—whether through miner signaling, a UASF, or a revised proposal—Bitcoin will emerge stronger, having demonstrated its ability to adapt to new threats. If it fails, the risk of gradual node concentration grows, potentially undermining the very property that makes Bitcoin valuable as a reserve asset.
In the words of Bruce Fenton, a long-time Bitcoin advocate, “The bigger risk is not a failure of this specific BIP; it is the growing centralization and financialization of the system over time.” BIP-110 may be a small battle in a long war, but how it ends will influence the war’s trajectory. For now, the community watches the signals, both on-chain and off.