Michael Saylor, the executive chairman of MicroStrategy and Bitcoin’s most vocal corporate advocate, just dropped a digital bombshell: 110 distinct reasons to oppose BIP-110, an as-yet-undisclosed Bitcoin Improvement Proposal. It’s a move that feels less like a technical critique and more like a declaration of war in a governance conflict that has been simmering for years. The tweetstorm landed with precision timing—right as the bull market euphoria is tempting developers to propose changes that could, in Saylor’s words, “destroy the very neutrality that makes Bitcoin trusted.”
But here’s the thing: nobody outside Saylor’s inner circle has actually seen the full BIP-110 text. The proposal remains shrouded in secrecy. What we do know is that Saylor is framing it as a cataclysmic threat to Bitcoin’s core value proposition—a meta-narrative that he, more than almost anyone, has helped build. How did we get here, and what does this conflict reveal about the future of decentralized governance?
To understand Saylor’s outburst, we need to step back into the mechanics of Bitcoin’s improvement process. BIPs are the lifeblood of protocol evolution—but they are also notoriously slow, deliberative, and consensus-dependent. Unlike Ethereum’s more agile EIPs, Bitcoin changes require near-unanimous support from miners, node operators, and the Core development team. This friction is intentional: it protects the network from capricious modifications. But it also creates a vacuum where powerful voices—like Saylor’s—can wield outsized influence without any formal voting power.
Saylor is not a miner. He is not a Core developer. He is a corporate holder with a massive Bitcoin stash (over 200,000 BTC as of last count). His influence stems from his role as a charismatic storyteller. In 2020, he single-handedly reframed Bitcoin as a “digital gold” asset suitable for corporate treasuries. That narrative turned a volatile crypto into a Wall Street darling. Now, he is using the same rhetorical weaponry to enforce a “no changes” policy—to preserve that digital gold status quo.
But what exactly is BIP-110? My analysis of the available signals—Saylor’s ten-word summary “threatens neutrality, sets bad precedent”—points in a disturbing direction. The proposal likely introduces discriminative transaction policies: perhaps a mechanism that allows miners or nodes to prioritize or block certain transactions based on content or origin. In plain language, it could be a backdoor for censorship. Saylor’s fear, which I share based on my experience auditing DeFi protocols in Prague, is that even a subtle rule change can erode the trust-minimized model that makes Bitcoin valuable.
Consider this: Bitcoin’s security does not come from code alone. It comes from the expectation that every transaction will be treated equally. If BIP-110 allows even a whisper of gatekeeping—say, flagging transactions from addresses linked to sanctioned countries—the entire house of cards wobbles. Institutional investors who bought the “no keys, no coins” spiel would suddenly wonder if the protocol is evolving into something that regulators can co-opt. That is the nightmare scenario Saylor is trying to pre-empt.
Build for humans, not just nodes. The core insight here is that governance battles are not just about code; they are about community identity. Saylor’s 110 reasons are not a technical audit—they are a value statement. He is telling other big holders: “I will fight anything that changes the rules we agreed on.” This is a classic conservative play in decentralized governance, and it reflects a deeper sociological split within the Bitcoin ecosystem.
Yet this conflict also reveals a blind spot in the “digital gold” narrative. Gold does not need upgrades. It does not require developers to fix scaling bottlenecks or improve privacy. Bitcoin, however, is a living network. Hard forks like SegWit and Taproot were controversial but ultimately beneficial. Saylor’s absolutism risks turning Bitcoin into a museum piece—a relic that cannot adapt to new threats like quantum computing or changing user expectations.
Let me pivot to a contrarian angle that many are too afraid to voice: What if Saylor is overreacting? My 2025 work with the EU regulatory task force taught me that proposed changes often look worse on paper than in practice. Without the full BIP-110 text, we are all operating on fear and assumption. Saylor might be exploiting this uncertainty to cement his personal brand as Bitcoin’s ultimate guardian. The “110 reasons” number is clearly theatrical—nobody drafts that many objections spontaneously. It is a calculated move to seize the narrative and force the proposal into a prolonged debate, during which it may quietly die.
But even if Saylor is posturing, the damage is real. The very act of debating neutrality opens a fissure in Bitcoin’s ideological bedrock. New investors who never questioned Bitcoin’s absolute permissionlessness will now wonder if it can be bent. That is the subtle poison of this event: it introduces doubt where none existed. In my Reclaim peer-support group during the bear market, I saw how quickly a single narrative shift can fuel panic. The psychological impact of governance uncertainty is often underestimated.
Education is the ultimate yield. What we need now is transparency. The BIP-110 authors should publish a full draft with a clear rationale. Saylor should release his 110 objections in a verifiable format, not as a tweetstorm. The community deserves to debate specifics, not fears. As a protocol PM, I have learned that sunshine is the best disinfectant for governance risk. If the proposal has merit, it will survive scrutiny. If not, it should be abandoned—not killed by FUD.
The takeaway is not about who wins this round. It is about how Bitcoin governance handles the next ten rounds. The bull market amplifies urgency, but it also amplifies ego. Saylor is a human, not a node, and his emotions are running the narrative. We must build systems that allow for reasoned evolution without sacrificing core trust. Otherwise, the greatest asset in crypto will freeze itself into irrelevance.
So, the question I leave you with is not whether BIP-110 passes. It is whether we, as a decentralized community, can separate legitimate technical progress from manufactured controversy. The most important update is the one that preserves trust, not just code.
