Community Trust ScoreVerified
Michael Saylor doesn’t want Bitcoin touching BIP 110. The Strategy chairman came out hard against the proposal, warning it could quietly erode what he sees as Bitcoin’s most valuable trait — its neutrality.
BIP 110, for those who haven’t been following the debate closely, would restrict transactions that carry data unrelated to payments. The idea is to cut down on what a chunk of the community calls “spam.” Proponents say the network gets clogged with non-payment data that has no business living on a monetary rail. They’ve pushed for a one-year limit on those transactions, framing it as a temporary, measured fix. But Saylor isn’t buying the framing. And he’s not alone in his skepticism.
What BIP 110 Actually Proposes
Strip away the technical language and BIP 110 is pretty much a filter. It would block — or at minimum, heavily restrict — transactions that include data not directly tied to a payment. The stated goal is network hygiene. Supporters argue that non-payment data inflates block space, slows things down, and crowds out legitimate financial transactions. One year, they say. Just give it one year and see if conditions improve.
But the framing of “one year” doesn’t fully settle the deeper argument. Critics point out that once you’ve established the precedent of restricting a category of transaction based on what the community thinks is appropriate usage, you’ve opened a door that’s very hard to close. The one-year window is almost beside the point.
That’s the part Saylor keeps coming back to.
Saylor’s Core Argument Against the Proposal
He’s not really arguing about spam. He’s arguing about something bigger — about who gets to decide what Bitcoin is for. Per Saylor, the real danger isn’t congestion or non-payment data cluttering blocks. It’s the idea that consensus rules can be changed because enough people disagree with how others are using the network.
That’s a different kind of risk. And it’s a harder one to quantify.
Bitcoin’s value proposition, in Saylor’s view, rests almost entirely on its neutrality. It doesn’t care who you are, where you live, or what you’re doing with your transaction — as long as it’s valid under the protocol. The moment you start carving out exceptions based on usage preferences, you’ve introduced a political layer into what was designed to be apolitical infrastructure. Saylor believes that’s a dangerous precedent to set, and he’s been vocal about it.
His concern isn’t hypothetical. The Bitcoin community has fought this battle before, in different forms. Debates over block size, over SegWit, over Taproot — each one revealed how fractious governance can get when stakeholders disagree about the network’s purpose. BIP 110 seems to be reopening that wound.
Not everyone sees it his way, obviously.
Some developers and long-time Bitcoin contributors genuinely believe that non-payment data — think Ordinals, inscriptions, certain token protocols built on top of Bitcoin — is a misuse of the network. They didn’t sign up to run infrastructure for digital collectibles or arbitrary data storage. They want a payment network. Clean, fast, and focused. BIP 110 is their attempt to push back.
But Saylor’s camp sees that push as fundamentally incompatible with Bitcoin’s design. You can’t have a censorship-resistant network that also censors. The contradiction is too obvious, they say. And once you’ve accepted that contradiction once, you’ve probably accepted it forever.
Where Things Stand Now
BIP 110 hasn’t been adopted. It’s still in discussion, still working its way through the community review process that Bitcoin proposals always go through. No formal decision has been made. No implementation timeline exists. The proposal needs broad consensus before anything changes — and broad consensus, in Bitcoin, is notoriously difficult to achieve.
That’s probably a feature, not a bug, depending on who you ask.
The slower the process, the more time there is to stress-test ideas like BIP 110 against Bitcoin’s foundational logic. Saylor’s opposition adds weight to the skeptical side of that ledger. Whether it’s enough to kill the proposal outright, or just delay it, isn’t clear yet.
What is clear: the debate isn’t going away. Bitcoin’s governance has always been messy, informal, and contentious. BIP 110 fits that pattern. It’s a fight about the soul of the network, dressed up as a technical proposal about transaction filtering. And Saylor, characteristically, isn’t softening his position.
He believes Bitcoin’s neutrality isn’t something you can partially compromise. It’s either there or it isn’t.
Hub: Bitcoin price, news, and analysis
Frequently Asked Questions
What does BIP 110 propose to do to Bitcoin transactions?
BIP 110 would restrict transactions containing non-payment data for a period of one year, targeting what some in the community call “spam” on the network.
Why does Michael Saylor oppose BIP 110?
Saylor argues the real risk isn’t spam — it’s that changing consensus rules based on disagreements over network usage threatens Bitcoin’s core neutrality and sets a dangerous precedent for future protocol changes.
