Woofun AI reports that the BIP-110 spam filter proposal faces imminent failure, with miner support languishing below 1% just four weeks before the mandatory signaling window opens around August 7. This collapse of momentum underscores a fundamental tension within the Bitcoin network: the clash between those seeking to curate on-chain data and the protocol’s inherent design to resist centralized rule changes. The rejection of this fork by key industry figures serves as a definitive case study in how governance inertia protects the network’s integrity against proposals that threaten its permissionless nature.

The authority behind this rejection stems from Adam Back, a figure whose credentials place him at the very origin of the technology. Back invented hashcash in 1997, a proof-of-work mechanism designed specifically to combat email spam, which was later cited in Satoshi Nakamoto’s white paper. Satoshi Nakamoto contacted Back directly during Bitcoin’s earliest developmental stages, establishing a lineage of trust and technical continuity. Back has spent nearly three decades embedded in cypherpunk networks and co-founded Blockstream, an infrastructure firm that employs several contributors to Bitcoin Core. His position is unique: the man who invented the original anti-spam mechanism is now instructing the anti-spam fork to stand down, lending significant weight to the argument that the proposed solution misunderstands the system it aims to protect.

Back’s objection is not rooted in a denial of the spam problem, but in a structural defense of decentralization. He argues that the very property making Bitcoin censorship-resistant money is its inability to allow any participant to impose preferences on others. In his view, a consensus rule that invalidates transactions some users find distasteful is "at its most basic a quest to police other people." The network’s immune system treats such attempts accordingly, rejecting them as violations of the core protocol. The same mechanism that prevents a government from filtering Bitcoin transactions also prevents BIP-110 supporters from doing so. There is no version of the network where only preferred filters are possible; the system is designed to be indifferent to content, ensuring that no single entity can dictate what constitutes valid data.

From a procedural standpoint, Back emphasizes that Bitcoin’s development relies on an IETF-style technical consensus model. In this framework, no change passes without surviving rigorous scrutiny from hundreds of developers and protocol reviewers. This resistance to change is not an obstacle to Bitcoin’s mission, but rather its primary protection. Back contends that BIP-110 failed this process, noting in an earlier post that the proposal "breaks multiple things" and lacks both technical and ecosystem consensus. The conclusion drawn from this logic is clear: supporters are free to fork and create their own chain, but the main chain is equally free not to follow. This permissionless structure ensures that no minority can force a change upon the majority.

Michael Saylor’s response reframed the stakes of this debate in terms of institutional risk. "There are 110 things more dangerous to Bitcoin than spam," the Strategy chairman wrote on X, arguing that "BIP 110 turns a spam dispute into a consensus change that would invalidate some currently valid, fee-paying transactions." Saylor, representing Strategy which holds the largest corporate Bitcoin treasury, highlighted that the entire institutional thesis rests on the assurance that validly acquired coins and valid transactions cannot be retroactively disfavored by a rule change. For the holders Saylor represents, that assurance is the product. A consensus mechanism that once invalidated fee-paying transactions because a faction disliked their content could, in principle, do it again with different targets, creating a precedent that undermines the security of the entire asset class.

The danger of this precedent lies in the potential to invalidate some currently valid, fee-paying transactions based on subjective criteria. If the network accepts a rule that allows for the retroactive disfavoring of certain transactions, it opens the door for future factions to target different types of activity. This creates a slippery slope where the definition of 'valid' becomes mutable, eroding the trust that underpins Bitcoin’s value proposition. Saylor’s argument is that the risk of establishing such a precedent far outweighs the nuisance of spam. The integrity of the ledger depends on the certainty that once a transaction is confirmed, it remains valid regardless of external opinions about its content.

Woofun AI data shows that miner signaling has been unambiguous in its rejection of the proposal. Miner support stood near 0.31% in late June, a figure drastically below the 55% threshold the proposal set for orderly activation. The Ocean pool produces most of the signaling blocks, yet no major pool has committed to the change, and F2Pool has refused outright. Because BIP-110 also carries a user-activated mandatory mechanism beginning around block 961,632, enforcing nodes could start rejecting non-signaling blocks in August regardless of miner support. This creates a significant chain-split risk: a minority chain running the new rules, surviving or fizzling based on whether exchanges and users assign it any economic value.

The root cause of this conflict lies in changes to OP_RETURN and the concerns of node operators. Since Bitcoin Core v30 relaxed the OP_RETURN relay limit in late 2025, non-financial data on the chain has grown significantly. A meaningful group of node operators sees this growth as drift from money toward database, arguing that the network is being used for purposes other than its intended financial function.

However, the past six months have demonstrated the difference between having a grievance and having consensus. Bitcoin changes only when thousands of independent operators choose to run the change, and on every measurable axis, they are choosing not to. The technical infrastructure remains aligned with the original vision of a neutral, permissionless ledger.

August will resolve the question mechanically, either through a dramatic shift in signaling or the opening of the mandatory window with a fraction of the network enforcing rules the majority ignores. The likely outcome is the creation of a low-hashrate side chain, which will serve as a demonstration of Bitcoin’s governance inertia. This event reinforces the notion that the hardest feature to fork is not the code, but the collective agreement of the network. The failure of BIP-110 proves that Bitcoin’s resistance to change is not a bug, but a critical feature that preserves its censorship-resistant nature.