When the graph spikes, the soul remains quiet. But when governance fights spill into the open, the silence breaks. Last week, Michael Saylor released a list of 110 objections to BIP-110. 110. That number is not random; it is a declaration of total war on a proposal he believes threatens the very soul of Bitcoin. The numbers surged—his tweet went viral, the hashtag trended—but the room felt empty of genuine technical debate. We were left with a manifesto, not a technical analysis. And that is exactly the problem.
To understand the stakes, we first need to understand BIP-110. It is a proposal for a temporary hard fork. In Bitcoin’s world, a hard fork is the equivalent of a constitutional amendment: it changes the rules of the network in a way that is incompatible with older versions. A temporary hard fork is even more radical—it introduces a time-limited change, then reverts. The stated goal, according to Saylor himself, is to improve Bitcoin’s scalability or security. But the method is controversial. Temporary hard forks require near-perfect miner coordination. If even a fraction of the hash power disagrees, the chain splits into two competing Bitcoin, each with a different history. That is not a patch; it is a divorce.
Saylor, the CEO of MicroStrategy and the largest corporate holder of Bitcoin, does not want that divorce. He outlined 110 reasons why BIP-110 should be rejected. The reasons themselves remain unpublished—he shared the target, not the bullet points. But the sheer volume tells us something. This is not a simple bug report. It is an organized campaign to stop a proposal before it gains momentum. From my own experience in protocol governance—auditing quadratic voting contracts at Gitcoin, where I saw how easily a well-intentioned mechanism could be gamed—I recognize the pattern. When a large stakeholder opposes a change, it is rarely because the change is technically unsound. It is because the change threatens their position. Saylor’s position is stability. He holds billions in Bitcoin. Any change that introduces uncertainty, even temporarily, devalues his asset.
But let’s look past the politics and examine the technical core. BIP-110 is a temporary hard fork. In my years as a Decentralized Protocol PM, I have seen temporary hard forks proposed for various reasons: to roll back a bug, to redistribute mining rewards, to test a new feature. Each time, the community hesitated. Why? Because the security assumptions break down. During a temporary fork, the old chain must be preserved—so full nodes need to run both versions. Miners need to coordinate an exact switchover time. If even 1% of miners continue mining the old version after the temporary fork ends, a permanent split can occur. It is like trying to glue two pieces of glass together; the joint is brittle. Based on my work in DeFi liquidity mining during the 2020 crisis, where we had to adjust reward distributions to avoid a rush of extraction, I learned that incentive alignment is everything. A temporary hard fork creates an incentive for miners to cheat. They can mine both chains, collect rewards from both, and then abandon the one that loses value. That is not theoretical; it is game theory.
Saylor’s opposition, therefore, is not just about his personal wealth. It is about network integrity. But here is the contrarian angle: Saylor’s overwhelming influence might itself be a threat to Bitcoin’s decentralization. He controls a gigantic treasury, but he is not a core developer. He does not write code. He does not mine. He is a powerful user who can sway public opinion with a single tweet. In the Gitcoin days, I learned that quadratic voting was designed to amplify many small voices, not one loud one. When one voice becomes too loud, the system tilts. Saylor’s 110 reasons could be technically valid, but because they come from him, they might be accepted without scrutiny. Conversely, if they are proven to be weak, it could damage his credibility—and by extension, MicroStrategy’s stance on Bitcoin. I recall my time standing against the royalty enforcement mechanism at Nifty Gateway, where I had to propose alternative solutions because the initial implementation was flawed. It was uncomfortable, but the debate improved the outcome. Here, we have no debate. We have a monologue.
Let’s examine what might be in those 110 reasons. Given Saylor’s background as a business strategist, they likely include arguments about: (1) Economic stability—a temporary hard fork could shake confidence in Bitcoin as a store of value. (2) Consumer protection—users might lose assets if the split is not handled properly. (3) Miner revenue—if the fork changes the reward schedule, miners might be disincentivized. (4) Development resources—the debate consumes energy that could be spent on other improvements. (5) Regulatory risk—a split could attract unwanted attention from lawmakers. Each of these has merit. But none are purely technical. They are political and economic. And in Bitcoin, where code is supposed to be law, that feels like a regression.
During the Terra/Luna collapse, I retreated into introspection. I questioned whether the entire industry was built on illusions. The lesson I took away was that we must separate the technology from the persona. BIP-110 is a technical proposal. It should be judged on its merits, not on who opposes it. Saylor’s reasons might be excellent. They might be flimsy. But because he has not released them, we cannot evaluate them. The community is left with a vacuum. And vacuums fill with speculation.
Here is what I think is really happening. Saylor is not just opposing a proposal. He is sending a signal to the market: “I will use my influence to maintain the status quo.” That signal has three effects. First, it reassures large investors that Bitcoin will not undergo radical changes. That is good for price stability. Second, it discourages innovation. If every major improvement faces the opposition of the largest holder, progress slows. That is bad for long-term network evolution. Third, it sets a precedent. Future proposals will need Saylor’s blessing, or they will face an uphill battle. That concentrates power in a single entity. And concentration of power is the antithesis of decentralization.
From my perspective as a protocol PM who has navigated governance battles—like the Uniswap v2 liquidity mining crisis where I refused to deploy incentives that rewarded speculation—I know that the best outcomes come from transparent, open debate. Saylor should release all 110 reasons. Then core developers should respond. Then miners should vote. That is the Bitcoin way. Instead, we have a cascade of tweets and a lack of substance. The graph spikes, but the soul remains quiet.
What should the community watch for? Miner signals. If major pools like F2Pool or Antpool publicly support or reject BIP-110, that will be the real tell. Also, watch the core developer mailing lists. If people like Pieter Wuille or Luke Dashjr weigh in, their technical authority will cut through the noise. And watch for Saylor’s next move: if he releases his reasons, we can finally analyze them. If he stays silent, we know this was never about technical details; it was about power.
In conclusion, this is a pivotal moment for Bitcoin governance. The risk of a hard fork is real, but perhaps not imminent. More acutely, the risk is that decision-making becomes centralized around a few whale voices. That would undermine the very trust that gives Bitcoin value. The takeaway is not to panic trade or pick a side prematurely. Instead, demand transparency. Insist that proposals and oppositions be backed by open data and code. Ethics are not a feature request; they are the protocol. Decentralization is a process, not a checkbox. Let’s not let one man’s 110 reasons shut down the conversation. Let’s use them to start a better one.