Michael Saylor’s 110-Point War on BIP-110: A Macro Watcher’s Dive into Bitcoin’s Silent Governance Crisis
The coffee was still hot in Condesa when the first tweet hit my timeline. Michael Saylor, the man who turned MicroStrategy into a Bitcoin treasury the size of a small nation, had just unloaded a 110-point critique against an obscure protocol upgrade — BIP-110. My group chat erupted. Everyone was reposting, retweeting, arguing. But nobody could tell me what BIP-110 actually proposed. That silence was louder than any chart pattern.
Let me back up. BIP stands for Bitcoin Improvement Proposal — the formal process for changing the Bitcoin code. Most are boring technical patches. But every few years, one gets political. Think of the Blocksize War. BIP-110 is a soft fork — backward-compatible, meaning old nodes still see new blocks as valid, but they can’t validate all the new rules. Soft forks sound safe, but they can reshape miner incentives, fee economics, and even censorship resistance. Saylor claims this one “causes more harm than it solves.” He listed 110 reasons.
I’ve been in crypto since the ICO days, and I’ve learned that when a whale with a $10B+ Bitcoin stash publishes a manifesto-sized objection, it’s rarely about code quality. It’s about control. Saylor is a maximalist: Bitcoin is the only asset worth holding. Any change that might dilute its “digital gold” narrative — even through a technical tweak — is existential to him.
Based on my years auditing DeFi protocols and watching governance battles, I believe BIP-110 likely touches one of two nerves: the block size limit or the fee market. Both are sacred cows. Increasing block size could lower fees but increase centralization pressure on node operators. Adjusting the fee market could shift miner revenue away from block rewards toward transaction fees — a delicate dance that the community has avoided since the halving schedule was set. Saylor’s 110 points probably argue that any change risks community fracture, miner revolt, or regulatory attention. He’s a businessman, not a developer — his arguments will be framed through risk, not throughput.
Here’s the contrarian angle: Saylor might be wrong. Or worse, he might be right for the wrong reasons. The crypto community loves to paint any opposition as FUD, but a 110-point list is a signal of deep engagement. Still, Saylor’s track record isn’t technical — he’s a sales guy who bet the company on Bitcoin. His objections could be driven by a desire to keep Bitcoin frozen in amber, protecting his own holdings from any innovation that might lower the barrier to entry or shift value away from L1. Remember, he’s not a core developer. The real power lies with the handful of maintainers on the Bitcoin Core repo and the miners who signal support. Saylor’s blast is noise — loud, well-funded noise — but noise nonetheless.
What does this mean for you, the macro observer? Watch the miners. If the top three pools — Foundry USA, Antpool, F2Pool — issue statements backing or opposing BIP-110, that’s the real signal. Saylor can tweet all day, but hash power votes with blocks. Also watch the Bitcoin Core pull requests. If the proposal gets merged into the next release candidate, Saylor’s opposition becomes irrelevant. If it stalls, his shot found its mark.
The takeaway? This isn’t about BIP-110’s technical merits — it’s about who gets to decide Bitcoin’s future. Saylor fired his shot. But in a system designed to be unstoppable, one man’s 110 points are just data points. The real story is the silence from the developers and miners. That’s where the signal lives. And if you want to position for the next cycle, ignore the tweetstorms. Watch the merge commits.
The signal is in the silence. The noise is just the market’s heartbeat — and right now, it’s skipping a beat over a proposal nobody can explain.