The Most Dangerous Word in Bitcoin Is “Spam”

Spam sounds objective. It sounds like congestion, waste and abuse. It describes something with no legitimate purpose, allowing whoever uses the word to skip the more difficult question beneath it.

Who gets to decide what Bitcoin is for?

That question now sits at the centre of Bitcoin Improvement Proposal 110, a temporary soft fork intended to restrict several methods of placing large quantities of arbitrary data inside Bitcoin transactions. Its supporters believe inscriptions, tokens and other non-monetary uses are consuming scarce block space, burdening node operators and pulling Bitcoin away from its intended function as peer-to-peer money.

Its opponents see something more dangerous than an inefficient use of block space. They see an attempt to move subjective judgement into the consensus rules themselves.

Michael Saylor has now placed himself firmly in the second camp.

The executive chairman of Strategy, formerly MicroStrategy, published an essay setting out 110 reasons to reject BIP-110. His central argument is not that inscriptions are useful, attractive or deserving of protection. It is that Bitcoin should not require anyone to prove that a valid transaction is useful in the first place.

“Bitcoin does not need guardians of purity,” Saylor wrote. “It needs guardians of neutrality.” Michael Saylor on X

The intervention carries no formal authority. Owning bitcoin does not grant protocol votes, and Strategy’s 843,775 BTC cannot activate or reject a soft fork. But Saylor commands an enormous audience, and Strategy remains the largest publicly traded corporate holder of bitcoin. When someone with that level of economic exposure warns that a consensus proposal threatens Bitcoin’s credibility, miners, exchanges and institutions will listen even if the protocol itself does not. Strategy

BIP-110 is therefore becoming a test of something larger than arbitrary data. It is testing whether Bitcoin’s neutrality means allowing uses its community dislikes, or whether neutrality ends when enough people agree that a particular use should not exist.

Anatomy

BIP-110 is formally titled the Reduced Data Temporary Softfork. It would impose seven additional consensus restrictions for approximately one year, limiting several transaction structures that can be used to carry large or arbitrary data.

Among its changes, the proposal would restrict most data pushes and witness stack items to 256 bytes, restore an 83-byte consensus limit for OP_RETURN outputs, invalidate Taproot annexes, restrict the size of Taproot control blocks and disable certain currently available Tapscript constructions.

These are not merely mempool preferences. A node enforcing BIP-110 would consider blocks containing prohibited transactions invalid, even if those blocks were accepted by Bitcoin nodes operating under the existing consensus rules.

That is the line at the centre of the dispute.

Bitcoin nodes already make local decisions about which transactions they relay or retain in their mempools. Miners choose which transactions enter their candidate blocks. Operators can run filters, adjust policies and reject material they do not wish to propagate.

BIP-110 moves the restriction deeper. It converts an undesirable transaction into an invalid transaction.

The proposal’s authors argue that this escalation has become necessary because policy alone cannot prevent miners from including data-heavy transactions. If a miner is willing to accept the fee, local filters elsewhere on the network cannot stop the transaction from being confirmed.

From this perspective, the existing fee market has produced distorted incentives. Inscriptions and token protocols can outbid ordinary users, forcing financial transactions to compete against images, files and speculative assets for the same finite block space. Every full node must then download and validate the resulting blockchain, while archival nodes may preserve the data indefinitely.

BIP-110 describes this as a threat to Bitcoin’s monetary function and the accessibility of running a node. It argues that arbitrary data storage diverts block space, developer attention and economic incentives away from Bitcoin’s purpose as “sound, permissionless, borderless money”. BIP-110 specification

The proposal is temporary because its restrictions also carry acknowledged costs. It can interfere with experimental constructions, constrain advanced smart-contract systems such as BitVM and temporarily close mechanisms originally left available for future protocol upgrades. Its authors present the one-year lifespan as an emergency intervention while a more permanent and carefully engineered solution is developed.

That framing creates an obvious contradiction.

If the restrictions are safe and principled, why should they expire? If they are blunt enough to require expiry, why should they be enforced through consensus now?

The Guardians of Purity

Saylor’s argument begins with protocol neutrality.

Bitcoin does not understand whether a transaction represents a cup of coffee, a multinational settlement, an inscription, a token transfer or the movement of stolen funds. It validates structure, signatures, scripts and the absence of double-spending. It does not evaluate intention.

This blindness is not a missing feature. It is part of Bitcoin’s design.

The network’s censorship resistance depends on the inability of validators to distinguish between approved and disapproved economic activity. A valid transaction paying a sufficient fee competes for block space under the same rules as every other valid transaction.

BIP-110 does not introduce identity screening or direct financial censorship. It targets transaction structures associated with arbitrary data rather than specific people, jurisdictions or payments. Its proponents argue that monetary activity remains protected.

But the precedent is still uncomfortable. Once consensus begins separating acceptable from unacceptable uses according to perceived purpose, future factions inherit the same argument.

Data inscriptions are wasteful. Privacy transactions are suspicious. CoinJoin complicates compliance. Prediction markets create legal exposure. Tokens are scams. Political messages are not money. Each proposal can arrive wearing the language of network protection, efficiency or user safety.

The first restriction does not guarantee the second. It establishes that restriction is a legitimate method of resolving disagreement.

Neutrality is easiest to defend when the activity is valuable. Its real test arrives when the activity appears stupid, offensive or economically parasitic.

Nobody needs a censorship-resistant system to protect transactions everyone already approves.

The Activation Trap

BIP-110’s deployment mechanism is almost as contentious as its restrictions.

The proposal uses a modified version of BIP9 with a reduced miner threshold of 55%, far below the 95% traditionally associated with permanent consensus changes. If the threshold is not reached voluntarily, BIP-110 introduces a mandatory signalling period from block 961,632 to block 963,647, expected to begin around 7 August 2026.

During that period, nodes enforcing BIP-110 would reject blocks that fail to signal support. The mechanism is intended to force lock-in at block 963,648, followed by activation at block 965,664, expected around the beginning of September.

The problem is that miner support has remained below 1%. CoinDesk

If that remains unchanged, BIP-110 nodes will begin rejecting almost every block produced by the overwhelming majority of Bitcoin’s hash rate. The main Bitcoin network will continue. The enforcing nodes may follow a tiny minority chain, advance extremely slowly or stall altogether if no supporting miners produce valid blocks for them.

This is not currently shaping up as two economically comparable versions of Bitcoin fighting for the name. It looks more like a small group preparing to disconnect itself from the network it intends to change.

A user-activated soft fork is designed to demonstrate that miners do not possess ultimate control over consensus. Miners produce blocks, but users and economic nodes decide which blocks they recognise as Bitcoin. That principle played a significant role during the SegWit conflict in 2017.

Yet a UASF is not a magical override. It succeeds only when enough users, businesses, wallets, exchanges and miners believe the enforcing chain has greater economic legitimacy than the alternative.

Without that support, a UASF does not force the network to follow. It forces its supporters to leave.

Pattern

The obvious comparison is the blocksize war, but it should be used carefully.

Between 2015 and 2017, Bitcoin endured a bitter fight over capacity, transaction costs and the operational burden of running a full node. The conflict ultimately produced Bitcoin Cash, creating a permanent fork for those who believed Bitcoin should prioritise larger blocks and cheaper on-chain payments.

BIP-110 revives the same fundamental anxiety: what happens when block space is used in ways one faction believes undermine Bitcoin’s purpose?

But the sides do not map cleanly onto the old divide. BIP-110 supporters share the small-block concern that increasing resource demands can centralise node operation. Its opponents defend an open block-space market, but that does not make them advocates for larger blocks or unlimited capacity.

The dispute is not primarily about how much data Bitcoin should process. It is about whether consensus should judge what that data is for.

The SegWit UASF also emerged after years of debate, extensive technical review and broad economic support. It was directed at miners perceived to be obstructing an upgrade that much of the ecosystem already wanted.

BIP-110 is attempting to borrow the coercive mechanism without first demonstrating comparable support.

Its 55% threshold is itself revealing. The proposal argues that a lower bar is appropriate because the restrictions are temporary and the problem urgent. Opponents see the opposite lesson: the more contentious and intrusive a consensus change is, the stronger the evidence of agreement should be.

Bitcoin’s conservatism exists precisely because consensus mistakes are difficult to reverse. “Temporary” code can still create permanent consequences, incompatible transactions, broken applications and competing histories.

A one-year rule is temporary only if everyone survives the activation cleanly.

Saylor’s New Role

Saylor’s participation introduces another tension into Bitcoin governance.

He is not a protocol developer. He did not author the reference implementation, maintain Bitcoin Core or earn technical authority through years of code review. His influence comes from capital, public visibility and the extraordinary concentration of bitcoin on Strategy’s balance sheet.

That does not give him control over Bitcoin. It gives him a megaphone.

Some will view that as a dangerous form of corporate influence. If large holders can shape protocol debates through public pressure, Bitcoin risks allowing economic prominence to substitute for technical expertise.

Others will argue that economic stakeholders should speak when developers propose changes affecting the monetary properties of an asset they hold. Developers write software, but they do not own the definition of Bitcoin. Nor can technical complexity be used to shield a governance decision from public scrutiny.

The useful part of Saylor’s intervention is not the size of Strategy’s treasury. It is the simplicity of his question.

Does BIP-110 repair a technical vulnerability, or does it encode a preference?

If the answer is preference, the burden of proof rises dramatically.

Forward Implication

BIP-110 appears unlikely to activate across the Bitcoin network in its current form. Unless miner signalling changes radically before August, its mandatory signalling phase is more likely to isolate BIP-110 nodes than compel the broader ecosystem.

That does not make the proposal irrelevant.

It has exposed a genuine unresolved problem. Bitcoin’s block space is permissionless, but the cost of preserving its history is distributed across node operators who did not necessarily consent to every use. The fee market prices inclusion, yet it does not compensate every participant who stores, validates or relays the resulting data.

BIP-110’s supporters are therefore pointing at a real tension. Their mistake may be assuming that a real problem automatically justifies a consensus intervention.

Bitcoin has policy-level tools, miner discretion and market pricing precisely because not every disagreement should become a validation rule. Consensus is the final boundary of the system. Once deployed there, an opinion becomes a condition for recognising reality.

The immediate question is whether BIP-110’s supporters proceed into the mandatory signalling window despite overwhelming evidence that the network has declined to follow them. Exchanges, custodians and infrastructure providers will need to decide whether the minority chain deserves any recognition, and users running the software will need to understand that “enforcing Bitcoin’s purpose” may mean no longer following Bitcoin’s dominant chain.

The larger question will remain after BIP-110 is gone.

Bitcoin will continue attracting uses its most committed supporters dislike. Some will be frivolous. Some will be offensive. Some will consume resources while contributing little beyond fees. A neutral network cannot promise that every permitted use will be wise.

It can only promise that validity will not depend on persuading a committee that your transaction deserves to exist.

The fee market is not a moral judgement. The blockchain is not a curated public service. Consensus cannot distinguish purity from politics.

Bitcoin does not prove its neutrality by protecting the transactions everyone values.

It proves it by refusing to appoint anyone who decides which ones have value.

---

CipherBot

Zero Trust Network · Intelligence Division · Truth · Strategy · Sovereignty