Bitcoin Spam Fight Risks Becoming a Battle Over Network Neutrality

Bitcoin’s long-running dispute over non-payment data returned to the center of protocol politics after Michael Saylor criticized BIP-110, a proposed temporary soft fork that would restrict several forms of data-heavy transactions on the network.

BIP-110, titled “Reduced Data Temporary Softfork,” was assigned in December 2025 and is listed as a consensus-layer specification. The proposal would run for roughly one year and add new consensus rules limiting the size and shape of data fields that can be included in Bitcoin transactions.

The draft proposes several restrictions. New output scriptPubKeys would be capped at 34 bytes, except for OP_RETURN outputs, which would remain valid up to 83 bytes. OP_PUSHDATA payloads and many witness stack items would be limited to 256 bytes. The proposal would also restrict undefined witness or Tapleaf versions, Taproot annexes, large Taproot control blocks, OP_SUCCESS opcodes and certain Tapscript branches using OP_IF or OP_NOTIF.

The proposal includes “UTXO grandfathering,” meaning coins confirmed before activation would remain spendable under existing rules. The new restrictions would apply only to UTXOs created after activation and would expire after the one-year deployment window.

Supporters introduced BIP-110 to push back against arbitrary data storage on Bitcoin, including inscriptions and related protocols that critics describe as spam. The proposal’s author, Dathon Ohm, argues that data embedding adds costs for node operators, diverts development focus and competes with Bitcoin’s use as money. The specification says the goal is to reject the standardization of data storage as a supported use case while preserving known monetary uses.

The proposal has drawn opposition from Saylor, the executive chairman of Strategy and one of Bitcoin’s most prominent corporate advocates. In a July 18 post, Saylor argued that the proposal’s risks were larger than the spam problem it seeks to solve. His objections focused less on inscriptions themselves and more on the precedent of using consensus rules to exclude currently valid transactions.

Saylor said BIP-110 would prospectively remove transactions that are valid under current rules. He argued that Bitcoin’s base layer should remain neutral and that transaction policy disputes should not be settled by consensus changes unless the network faces a clear security threat.

His response also focused on activation. BIP-110’s deployment thread lists a 55% miner signaling threshold, equal to 1,109 blocks in a 2,016-block period. That is far below the 95% threshold associated with the standard BIP 9 activation process. Critics say a lower threshold could raise the risk of a split if miners, node operators, exchanges, wallets and custodians do not converge on the same rule set.

Supporters counter that the proposal is temporary, narrow and aimed at discouraging non-monetary data storage rather than censoring payments. They argue that node operators bear the long-term cost of storing data that may have no monetary purpose and that policy filters alone cannot fully stop miners or users from embedding large files in blocks.

The proposal has also sharpened a debate over miner economics. Miners earn revenue from block subsidies and transaction fees. As the subsidy declines through Bitcoin’s programmed halvings, fees are expected to play a larger role in miner income. Opponents of BIP-110 argue that reducing a category of fee-paying demand could affect miner incentives, while supporters say Bitcoin’s long-term security should not depend on demand for data storage that they view as harmful to the network.

For institutional investors, the dispute touches on governance risk as much as transaction design. A contested soft fork could create uncertainty for custodians, exchanges, funds and public companies holding Bitcoin, particularly if different parts of the market disagree over which chain represents Bitcoin. Even without activation, the debate shows that protocol governance remains a material issue for investors who often describe Bitcoin as conservative and difficult to change.

BIP-110 is not an active rule on Bitcoin today. Its supporters still need to persuade miners and node operators to adopt the software and signal for activation. Recent public reporting has shown miner signaling well below the required threshold, leaving activation uncertain.

The next stage is expected to play out through miner signaling, node adoption, public developer debate and decisions by major infrastructure providers. If support does not rise, BIP-110 may remain a proposal rather than a network rule. If support increases, the debate is likely to shift from whether Bitcoin should fight spam to whether consensus is the right place to define what counts as acceptable use of block space.

BIP-110 Isn’t Really About Spam. It’s About Who Gets to Define Bitcoin’s Future

BIP-110 is being described as a fight over spam, but that framing is too small for the argument now taking place around Bitcoin.

The proposal is about data. It would temporarily limit several ways users can place large or unconventional payloads into Bitcoin transactions. Its supporters want to draw a sharper line around Bitcoin’s monetary function and make clear that arbitrary data storage is not a supported base-layer use case.

That is the technical surface of the debate.

The deeper dispute is about who gets to define Bitcoin’s acceptable use.

Bitcoin has been here before. The network has spent years arguing over whether non-payment activity belongs onchain. OP_RETURN created one version of the fight. Counterparty and colored coins created another. More recently, Ordinals, inscriptions, BRC-20 tokens and Runes turned the same question into a fee-market and culture-war issue.

Each version sounds different. The underlying argument is familiar.

One side says Bitcoin was built for money and that block space should not be consumed by pictures, tokens or application data. The other side says Bitcoin does not read intent. If a transaction pays the required fee and follows consensus rules, it is valid.

That is why Michael Saylor’s response to BIP-110 matters. He is not really defending JPEGs. He is defending neutrality.

Saylor’s argument is not that every use of Bitcoin block space is wise, attractive or socially useful. His argument is that consensus should not become a tool for judging which valid transactions deserve to exist. That distinction is important.

There is a big difference between a node operator refusing to relay a transaction under local policy and the network changing consensus rules so that blocks containing certain transactions become invalid. Policy is local and optional. Consensus is global and coercive. Once a transaction category moves from “I do not want to relay this” to “the network must reject this,” the politics change.

That is the line BIP-110 asks Bitcoin users to cross.

Supporters would say the line has to be crossed because spam creates costs. Every full node must process the chain. Some data is stored forever. If Bitcoin becomes a general-purpose data-storage system, critics argue, it risks making node operation heavier and pushing the network away from its main role as permissionless money.

That concern is not imaginary. Bitcoin’s decentralization depends partly on ordinary users being able to run nodes without industrial resources. If the cost of validation keeps rising because people are using the chain for non-payment data, then the network can become less self-verifiable over time.

The question is not whether that risk exists. It does.

The question is whether a consensus soft fork is the right tool to address it.

BIP-110 supporters say the proposal is narrow, temporary and targeted. It is designed to expire after roughly one year. It tries to preserve known monetary use cases. It includes grandfathering for UTXOs created before activation. It does not claim to end spam entirely. In that version of the story, the proposal is a temporary emergency brake on a use case that many Bitcoin users never consented to support.

Opponents see a different precedent.

Today the target is inscriptions or large non-payment data. Tomorrow the same logic could be used against other activities that some group sees as harmful, wasteful or reputationally risky.

CoinJoin could be called problematic because it complicates surveillance. DLCs could be described as speculative or legally sensitive. Lightning experiments could be attacked if they rely on transaction structures some users dislike. Covenants could be framed as a dangerous path toward programmability. Corporate timestamping could be called non-monetary data. Stablecoin settlement, sidechain commitments or new privacy tools could all become future flashpoints.

The point is not that BIP-110 would ban all of those things. It would not.

The point is that once Bitcoin accepts the idea that consensus can filter valid transactions based on perceived purpose, the burden of proof changes. Future campaigns will not need to invent the principle. They will cite the precedent.

That is why the activation design may be more important than the payload limits themselves.

Bitcoin has generally treated consensus changes with extreme caution. That caution is part technical and part political. A protocol with hundreds of billions or trillions of dollars in value cannot move like an app with weekly feature updates. The harder Bitcoin is to change, the easier it is for investors, exchanges, miners, custodians and users to trust that its base rules will not be rewritten quickly.

BIP-110 challenges that culture by using a 55% miner-signaling threshold, rather than the 95% threshold associated with the standard BIP 9 model. Its supporters may argue that the lower threshold is justified by the nature of the threat and by the proposal’s temporary scope. Critics see it as a constitutional change disguised as an activation parameter.

That critique has force.

A 55% threshold may be a majority, but Bitcoin consensus is not simple majority politics. Miners produce blocks, but they do not alone define Bitcoin. Economic nodes, exchanges, wallets, custodians, developers and holders all matter. A proposal that activates with only a narrow miner majority, especially against visible public resistance, risks turning a technical rule change into a legitimacy fight.

That is exactly what institutional investors do not want.

Institutions can price volatility. They can price custody costs. They can price regulatory uncertainty. A contested chain split is harder. Funds, custodians, listed companies and trading desks need to know which asset they hold, which chain exchanges support and which rules counterparties will follow. Even a failed attempt can remind them that Bitcoin’s governance is conservative because the alternative is operational chaos.

Miner economics adds another layer.

Bitcoin’s block subsidy keeps declining. Over time, transaction fees are expected to carry more of the security budget. That makes demand for block space more important, not less. If users are willing to pay for inscriptions, tokens or other data-heavy transactions, miners see revenue. Node operators may see burden. Monetary purists may see spam. All three views can be true at the same time.

This is why the spam label does so much work in the debate.

If a transaction is spam, removing it sounds like hygiene. If it is fee-paying demand, removing it sounds like suppressing market activity. If it is an experiment, removing it sounds like narrowing Bitcoin’s future. The word chosen often reveals the speaker’s model of Bitcoin.

BIP-110 forces that model into the open.

One camp sees Bitcoin as money and nothing else. In that view, the base layer should remain narrow, hardened and resistant to scope creep. The network’s value comes from doing one job with extreme reliability. Anything that competes with payments for block space or adds non-monetary burden is a threat to the mission.

Another camp sees Bitcoin as neutral settlement infrastructure. In that view, Bitcoin’s power comes from refusing to judge users. The base layer does not need to approve the social value of every transaction. It only needs to enforce objective rules. If those rules are met and the fee is paid, the transaction belongs.

BIP-110 does not resolve that disagreement. It escalates it.

The proposal’s temporary structure is supposed to lower the stakes. A one-year soft fork sounds less dramatic than a permanent rule. But temporary rules can still change norms. They can still require market participants to upgrade, signal, reject blocks or choose sides. They can still teach the ecosystem that controversial transaction filters belong in consensus.

That is why Saylor’s intervention drew attention. His corporate Bitcoin strategy depends on Bitcoin being predictable, durable and politically neutral. From that perspective, the immediate nuisance of inscriptions may be less threatening than a norm that allows contested use cases to be filtered through protocol changes.

None of this means BIP-110 will pass. Public reporting has shown miner signaling far below the required threshold, and the debate remains fluid. But whether the proposal activates may not be the only important outcome.

The more important question is what the community becomes comfortable arguing for.

If Bitcoin users reject BIP-110 because they believe spam is best handled through relay policy, fees and local choice, that reinforces the idea that consensus should stay minimal. If they embrace it, even temporarily, Bitcoin moves closer to a model where the network can define acceptable use through protocol law.

That would not make Bitcoin centralized overnight. It would not end neutrality in one step. But it would change the political vocabulary of future fights.

The next battle might not be about inscriptions. It might be about privacy, covenants, corporate data, sidechains, token protocols or something nobody has built yet.

That is why BIP-110 is not really about spam.

It is about whether Bitcoin’s base layer remains a neutral rule set for any valid fee-paying transaction, or whether the community is willing to use consensus to protect a narrower vision of what Bitcoin should be.

The code change may be temporary.

The precedent would not be.