The Logic of Spam: David Schwartz, BIP-110, and the Fault Line in Bitcoin's Governance

The code spoke, but the logic was a lie. David Schwartz, former CTO of Ripple and architect of the XRP Ledger consensus algorithm, took aim at what he called Bitcoin's "spam purists." His words were sharp, clinical. He referenced the failure of BIP-110 as evidence that Bitcoin's governance—its very mechanism for change—is broken, captured by a faction that prioritizes ideological purity over technical progress. The response from the Bitcoin community was predictable: a mix of dismissal, anger, and counter-accusations. But beneath the noise lies a deeper structural fault line, one that has been widening since the Ordinals boom of 2023. Context: The Bitcoin Spam Debate At its core, the current controversy is about what belongs in a Bitcoin block. The "spam purists" argue that Bitcoin's block space should be reserved exclusively for monetary transactions—peer-to-peer transfers of value. Non-financial data, such as inscriptions or metadata, is considered "spam" that degrades the network's primary function. On the other side, the pragmatists, or "cando-purists" as Schwartz calls them, argue that any transaction paying an appropriate fee has a right to be included. The market should decide, not a moral committee. This debate is not new. It dates back to the early days of Bitcoin, when the community argued over the use of OP_RETURN for storing small amounts of data. But the controversy exploded with the advent of Ordinals and BRC-20 tokens, which turned Bitcoin into a platform for NFTs and memecoins. The resulting congestion pushed transaction fees to levels that priced out many traditional users, creating a real economic tension. BIP-110, whatever its exact content, was a proposed solution to this tension. According to Schwartz, it failed. He did not provide details, but the implication is clear: the purists, who hold disproportionate influence over the Bitcoin Improvement Proposal process, blocked it. The failure of BIP-110 is not just a technical setback; it is a symptom of governance paralysis. But here is where the facts get murky. A quick check of the Bitcoin BIPs repository reveals that BIP-110, as officially numbered, is not a proposal about spam filtering at all. It is a minor change to the protocol related to the BIP process itself. This discrepancy raises a critical question: is Schwartz referring to a different proposal, or is he misremembering the number? Or is the article citing him incorrectly? The lack of context is a red flag. Trust is a variable you cannot hardcode. Core: A Systematic Teardown of Bitcoin Governance To understand the significance of this spat, we must set aside the personalities and examine the underlying mechanics. Bitcoin's governance is not a formal democracy. It is a collection of loosely coupled stakeholders: core developers, miners, node operators, exchanges, and users. The BIP process is supposed to be a meritocratic pipeline for proposing, discussing, and implementing changes. In practice, it is a bottleneck. Anyone can submit a BIP. But for it to be considered, it must survive a gauntlet of reviews, objections, and—most importantly—social consensus. This is where the "purists" wield power. They are not a majority, but they are loud, well-funded, and technically respected. They control the narrative in the Bitcoin-dev mailing list and on GitHub. They can stall a proposal indefinitely by raising endless objections, demanding more analysis, or simply refusing to merge code. This is not unique to Bitcoin. Every open-source project faces similar dynamics. But in Bitcoin, where the stakes are billions of dollars and the ethos is "don't break things," the inertia is institutionalized. The result is a system that strongly favors the status quo. Any proposal with even a whiff of controversy—such as BIP-119 (CTV) or BIP-118 (SIGHASH_ANYPREVOUT)—has been stuck in limbo for years. Based on my own due diligence experience auditing blockchain governance models, I can confirm that this is a classic case of "the tyranny of the minority." A small, highly motivated group can block change even if the majority of silent stakeholders would benefit from it. The "spam purists" are a textbook example: they possess the technical expertise to veto any proposal that threatens their vision of Bitcoin as a pure monetary network. But the contrarian truth is that the purists have a point. If you allow arbitrary data into Bitcoin blocks, you are effectively turning the world's most secure timestamping service into a cheap storage layer. That could degrade its reliability over time. The Ordinals frenzy demonstrated that the cost of being permissive is real: fees spiked, ordinary users were priced out, and the network confirmed a flood of meaningless transactions. The purists argue that the market, left to itself, will not correct this externality because the immediate profit from inscription survives the long-term damage to the network's brand. Yet the purists' solution—protocol-level censorship—is equally problematic. It introduces a new form of centralized control, where a handful of developers decide what is "spam" and what is not. That is a slippery slope. Once you start filtering, where do you stop? Can you filter transactions that fund terrorism? Or transactions that support political activism? The line between judgment and enforcement is thin, and Bitcoin's censorship resistance is not divisible. They built a palace on a fault line. Contrarian Angle: What the Bulls Got Right Despite the alarmism, the Ordinals boom has had a net positive effect on Bitcoin's security. Higher fees mean higher miner revenue, which strengthens the network's security budget for the post-subsidy era. The inscriptions have also attracted a new generation of developers to Bitcoin, spurring innovation in layer-2 solutions and smart contract capabilities. The market is voting with its feet: over 60 million inscriptions have been created, representing billions of dollars in transaction fees. That is not spam; it is demand. Moreover, the threat of protocol-level filtering is unlikely to materialize. The Bitcoin Core developers are aware of the risks of censorship. The loudest voices among the purists may advocate for changes, but they do not have the power to unilaterally impose them. Any modification to the Bitcoin protocol requires broad consensus, and the node operators—who ultimately run the software—are unlikely to accept a version that restricts their freedom to include transactions. Data does not lie, but it does not care. Takeaway: The Accountability Call The Schwartz-puriest debate is a microcosm of a larger struggle: the tension between ideological purity and practical evolution. Bitcoin's governance is not a machine; it is a messy, human process. The failure of BIP-110, if it truly failed, is not a disaster. It is a normal part of the iterative, conflict-driven progress that has kept Bitcoin secure for 15 years. But the question remains: Can Bitcoin evolve fast enough to survive the next decade? Or will its governance sclerosis drive innovators to other chains—like XRP Ledger, which claims to offer faster, more responsive upgrades? Schwartz's critique is a warning, not a victory lap. He is pointing out that the palace is built on a fault line, and the earthquakes are getting stronger. The code spoke, but the logic was a lie. The only truth is that you cannot hardcode trust. You have to earn it, block by block.