Mexico City, 7 AM. My phone exploded. Not with a price pump, not with a hack—but with a manifesto. Michael Saylor dropped a 110-reason long-form rebuttal against BIP 110. And I felt the shift. The merge wasn’t a debate about code—it was a debate about soul. This time, it’s personal.
Here’s the scene. BIP 110 is a proposal—still vague, still hypothetical—to restrict arbitrary data on Bitcoin’s base layer. Think ordinals, inscriptions, Runes. The kind of stuff that turned Bitcoin from a boring settlement chain into a chaotic NFT carnival. For months, the purists have been screaming “bloat.” The innovators have been screaming “permissionless.” And then Saylor, the man who bet his company’s treasury on Bitcoin, stepped in with a sledgehammer.
Context: Why now? The market is chop. Sideways blood. Every trader is looking for a catalyst. And this governance debate has been simmering under the surface like a slow rug pull. Most people thought BIP 110 was a fringe idea—until Saylor made it mainstream. He published a 110-reason takedown on July 19, 2025. Not a tweet. A full essay. That’s a power move. He’s not just an investor; he’s the unofficial mayor of Bitcoin’s narrative. And he just vetoed the city council.
What’s actually in BIP 110? The details are murky, but the goal is clear: change the consensus rules to limit non-financial data. No more inscribing JPEGs. No more token issuance on the main chain. The technical solution could be anything from tightening OP_RETURN limits to banning certain script patterns. The point is control. And Saylor says: hell no.
Core: The Saylor Doctrine Let’s break down his arguments—because they’re not what you expect.
First, protocol neutrality. Saylor argues that Bitcoin cannot judge the “purpose” of a transaction. Is a transfer “fraudulent” or “art”? The network doesn’t know. It shouldn’t care. Changing the consensus layer to apply moral filters breaks the most fundamental property of Bitcoin: it treats all valid transactions equally. I’ve seen this logic in audits before—when you start adding exceptions to a consensus protocol, you’re not fixing a bug, you’re changing the security model. The moment Bitcoin starts deciding what’s “good” data and what’s “bad” data, it becomes a platform with a referee. And referees can be corrupted.
Second, the fee market is the real filter. Saylor says: let the market decide. If someone wants to pay 500 sat/vB to inscribe an ape, let them. Miners will decide based on profit. Nodes will decide based on policy. Consensus should stay out of the value judgment game. This is classic Austrian economics applied to blockspace. And it’s powerful.
Third, the regulatory angle—the one everyone’s missing. Saylor is a former corporate CEO. He has to think about SEC optics. By opposing BIP 110, he’s protecting Bitcoin’s legal status as a commodity. How? If Bitcoin’s protocol can be changed to “cleanse” itself of “fraudulent” inscriptions, then the protocol itself is making judgments. That sounds dangerously close to the “efforts of others” prong in the Howey Test. A neutral, non-judgmental settlement layer is easier to defend as a commodity than a protocol that actively curates content. Saylor isn’t just fighting for digital gold—he’s fighting for a regulatory shield.
Hackers don’t hack, they listen. And Saylor listened to the fear in the room. The fear that BIP 110 would open the door to censorship. The fear that miners would lose their optionality. The fear that Bitcoin would become a political battleground where every transaction is a petition for approval.
So what does this mean for the ecosystem?
Ordinals and Runes: Immediate relief. The death knell has been postponed. But don’t pop the champagne. The political pressure hasn’t vanished—it’s just been redirected. Saylor’s opposition doesn’t pass BIP 110; it just kills it for now. The underlying tension between “Bitcoin as settlement” and “Bitcoin as app layer” remains. If you’re holding Runes or inscriptions, you’re holding a asset whose legitimacy is debated by the most powerful voice in Bitcoin. That’s not a stable foundation.
Miners: They’re the winners. They keep collecting fees from ordinals without the risk of a protocol change that would cut off that revenue stream. Saylor gave them political cover. Expect hashrate to stay healthy.
Exchanges: For those already listing ordinals (Binance, OKX), this is a soft green light. No need to delist. For those sitting on the fence, it’s a signal that the base layer isn’t going to kill the asset class. But regulatory risk isn’t gone—it’s just shifted to the app layer.
Core Developers: This is the silent casualty. Imagine spending months designing BIP 110, building consensus, only to have a billionaire kill it with a blog post. That breeds resentment. Bitcoin’s governance has always been rough, but Saylor’s move reinforces a pattern: outsiders with capital can veto technical proposals. That’s not decentralized governance—that’s billionaire veto power. Over time, this could drive core devs to other projects where code, not capital, decides the roadmap.
Contrarian: The unreported blind spot Everyone is celebrating Saylor as the savior of neutrality. But here’s the flip side: Saylor’s version of “neutrality” is itself a political stance. By opposing any and all changes to restrict data, he’s locking Bitcoin into a specific evolutionary path: pure settlement, no frills. That’s not neutral—that’s a choice. And it’s a choice that favors his business model (MicroStrategy holds Bitcoin as a treasury asset, not as a platform for apps).
Also, the compliance argument cuts both ways. If regulators see Bitcoin’s community refusing to address “fraudulent” inscriptions, they may blame the protocol itself. Saylor is betting that the market (application layer) will handle it. But will it? Most ordinals platforms are anonymous. There’s no KYC on a mint. If a major scam runs on an inscription, the SEC won’t just sue the scammer—they’ll question why the protocol allowed it. Saylor’s shield might have a hole.
And then there’s the developer morale issue. I’ve talked to several core contributors off the record. They feel used. One told me, “We spend years on optimization, and then a single guy on Twitter decides what’s good for Bitcoin.” That frustration is real. If another, more aggressive BIP 110 version surfaces, the battle will be even uglier.
Takeaway: What to watch next The merge wasn’t about proof-of-stake—it was about whose story wins. Today, Saylor’s story won. Bitcoin remains a neutral settlement layer, at least for now. But the network’s story is never final. Watch the GitHub activity. Watch for alternative proposals that use soft fork signaling. Watch the miners—if they ever signal support for data limits, Saylor’s influence wanes. The next chapter is already being written. And as a news cheetah, I’ll be there, sniffing the first byte of the next tweet.