110 reasons. That is how many objections Michael Saylor publicly filed against BIP-110 last week. For a protocol that prides itself on code over opinion, this is an anomaly worth examining.
Saylor, the Executive Chairman of Strategy (formerly MicroStrategy), holds over 200,000 Bitcoin on his company's balance sheet. He is not a developer. He is not a miner. He is a shareholder—one with an outsized microphone. His 110-point manifesto against an undisclosed BIP is a governance event, not a technical one. Yet it reveals a structural fracture in Bitcoin's decision-making process that has been papered over for years.
Let me be clear: the technical details of BIP-110 remain unknown. No draft has been published on the Bitcoin-Dev mailing list. No GitHub pull request exists. The only signal is Saylor's opposition, centered on two claims: the proposal threatens network neutrality and establishes a censorship precedent. From my experience auditing over a dozen DAO governance systems, I can tell you that when a major stakeholder resorts to a flood of objections without releasing the proposal text, the game is not about code—it is about power.
Context: The Governance Vacuum
Bitcoin's governance is often described as 'rough consensus.' There is no formal voting body. BIPs are submitted, discussed, and if no clear opposition emerges, they may be merged by maintainers. Miners signal via block versions. Node operators choose whether to upgrade. This system worked for uncontroversial upgrades like SegWit, but it is brittle when faced with fundamental disagreements.
Saylor's response illustrates the brittleness. By issuing 110 reasons, he effectively drowns the proposal in narrative noise. He does not need to show code flaws; he only needs to raise enough doubt to prevent consensus. This is a classic veto-by-FUD tactic. And it works because Bitcoin has no mechanism to resolve disputes except for a popularity contest among whales and miners.
Core: The Data Behind the Noise
Let me strip away the rhetoric and look at what we actually know. Based on public data and my own risk modeling, the following facts are verifiable:
- BIP-110 is likely related to transaction ordering or filtering. The term 'neutrality' is code for 'treating all transactions equally.' Any modification to how miners select or validate transactions could be seen as introducing bias.
- Saylor's opposition aligns with the 'digital gold' camp, which resists any change that might enable new use cases (e.g., smart contracts, privacy) because such changes could complicate the regulatory narrative.
- The probability of BIP-110 being implemented is low—below 10% in my estimation—unless it has vocal support from prominent developers or mining pools. So far, silence from both groups.
But the real insight is not about BIP-110 itself. It is about the structural weakness exposed. In decentralized systems, governance is a liability. When a single actor can command media attention for a proposal no one has seen, the protocol's resilience is tested. From my work on DAO governance templates, I have seen this pattern before: a minority with large token holdings blocks upgrades not based on merit but on fear of diluting their power. Code is the only law that holds, but only if you can read it. Most market participants cannot evaluate BIP-110. They trust Saylor. That trust is an attack surface.
Contrarian: The Danger of Status Quo Dogma
Conventional wisdom paints Saylor as a defender of Bitcoin's purity. I argue the opposite. By opposing any change without due examination, he promotes a form of ossification that could eventually render Bitcoin irrelevant. Consider Ethereum: its ability to upgrade (e.g., Merge, EIP-1559) has kept it adaptable. Bitcoin's refusal to evolve may preserve its 'sound money' narrative, but it also cedes ground to protocols that can implement privacy or scalability features.
Skepticism is the first line of defense. I apply it to all claims, including Saylor's. His 110 reasons are not peer-reviewed; they are a press release. If BIP-110 were genuinely dangerous, the rational response would be to publish a single, detailed technical critique—not a list of talking points. This suggests the proposal may be less harmful than he implies, or that his real concern is political, not technical.
Moreover, the 'censorship precedent' argument cuts both ways. By using his platform to preemptively suppress discussion, Saylor himself engages in a form of censorship. Governance isn't a popularity contest; it's a verification process. Without transparent verification, the network loses its most valuable asset: trust.
Takeaway: Governance Is the Real Protocol
Bitcoin's next upgrade may not be a soft fork—it may be a governance reform. BIP-110 will likely fade into obscurity, but the structural tension will remain. How do you upgrade a decentralized network when a single whale can veto unilaterally? The answer is not clear. But pretending the problem does not exist is a recipe for stagnation. Verify everything, trust nothing. That includes the messengers, especially when they carry 110 reasons.