On an otherwise unremarkable Tuesday in late 2026, Michael Saylor posted a thread. It contained exactly 110 bullet points. Each point was a reason to reject BIP-110. The thread went viral within minutes. But here is the anomaly that caught my attention: the technical content of that thread remains undisclosed. The asset manager who controls the largest corporate Bitcoin treasury—over 226,000 BTC—chose to signal opposition without publishing a single line of code analysis. The ledger remembers what the narrative forgets. And in this case, the narrative forgot to ask: what are those 110 reasons?
Context: The Proposal and the Protector
BIP-110 is a Bitcoin Improvement Proposal that proposes a temporary hard fork. The exact mechanism is still debated in developer circles, but the core goal is to introduce a periodic recalibration of the mining difficulty adjustment algorithm. Proponents argue that the current difficulty algorithm lags during rapid hash rate fluctuations, creating periods of excessive block times or premature subsidy reductions. The proposal aims to insert a 'checkpoint' every 2,016 blocks that re-anchors the difficulty to a moving average, effectively creating a soft floor for block production time.
Michael Saylor is not a developer. He is not a miner. He is a corporate treasurer who bought Bitcoin when it was below $5,000. His company, MicroStrategy, now holds more Bitcoin than any publicly traded entity. His public stance on protocol changes has historically been conservative: maintain the status quo, avoid any change that could introduce uncertainty, treat Bitcoin as a digital store of value first and a payments network second. His opposition to BIP-110 aligns with that pattern.
But listing 110 reasons without technical disclosure is a strategic move. It signals that the opposition is not merely emotional; it is systematic. It also ensures that the debate remains at the level of narrative rather than code. And that, from a governance perspective, is a dangerous game.
Core: Reconstructing the Protocol from First Principles
Let me be clear: I have no access to Saylor's 110 points. But based on my experience auditing protocol upgrades—including the 2020 Curve Finance stableswap invariant that had a rounding error in the virtual price calculation—I can reconstruct the likely technical objections from first principles.
A temporary hard fork introduces a discontinuity in the blockchain's state. The word 'temporary' is misleading; in cryptographic terms, there is no such thing as a temporary change to consensus. Any hard fork permanently splits the blockchain into two chains unless the entire network upgrades simultaneously. Bitcoin does not have a mechanism for simultaneous upgrades. The upgrade must propagate over weeks or months, creating two chains that can diverge if miners disagree.
The first hidden reason, then, is the risk of two Bitcoins. If a majority of miners adopt BIP-110 but a significant minority refuse, the network splits. The market then has to price two assets. That uncertainty is unacceptable for a corporate treasury holding $15 billion in Bitcoin. Saylor's 110th reason is likely: "This upgrade creates a chain split scenario that violates the fundamental promise of a single, immutable ledger."
The second hidden reason concerns the difficulty recalibration itself. BIP-110's checkpoint mechanism would give miners a periodic tool to manipulate block times. Consider the math: the current difficulty adjustment looks at the actual time difference between the last 2,016 blocks. If miners can predict when the checkpoint occurs, they can temporarily reduce hash rate before the checkpoint to lower difficulty, then surge hash rate after to mine more coins at lower cost. This is a textbook game-theoretic vulnerability. I saw a similar pattern in the Terra/Luna collapse aftermath when I reverse-engineered the LUNA token's algorithmic stabilization mechanism in 2022. The recursive debt accumulation relied on an assumption that arbitrageurs would always act to restore the peg. But when the cost of arbitrage exceeded the reward, the system broke. BIP-110's checkpoint assumes miners will act cooperatively, not strategically.
The third hidden reason is the governance precedent. If a temporary hard fork can be activated by a simple majority of miners, then what stops the next proposal from being a permanent block size increase, or a change to the subsidy schedule? Saylor is protecting the user by opposing the foot-in-the-door approach. Stability is not a feature; it is a discipline. Once you accept that the protocol can be modified via hard forks, every subsequent upgrade becomes easier to push through, eroding the immutability that makes Bitcoin valuable.
But here is where the contrarian angle emerges.
Contrarian: The Blind Spot of the Silent Guardian
Saylor's opposition is framed as protection. But protection from what? From change itself. And that is a dangerous posture for a technology that has survived precisely because it could evolve. The 2017 SegWit upgrade was contentious. The 2017 Bitcoin Cash fork was messy. But SegWit enabled second-layer scaling. The protocol adapted.
Saylor's 110 reasons may be a shield against bad design, but they also function as a wall against innovation. If every proposal must survive the veto of a single large holder, then Bitcoin's governance becomes plutocratic, not democratic. The ledger remembers what the narrative forgets: the narrative of 'digital gold' was built not by freezing the protocol, but by carefully expanding its use cases.
Consider the actual cost of rejecting BIP-110. If the proposal solves a real problem—say, reducing the variance in block times during hash rate drops—then rejecting it condemns the network to inefficiency. Miners in regions with low-cost energy will have an advantage because they can endure longer block intervals. Users will face unpredictable confirmation times during stress events. And all of this is acceptable because a corporate whale says 'no'.
I recall from the Ethereum whitepaper deconstruction I did in 2017: the gap between theory and implementation is where the real risks live. BIP-110 may have flaws. But without public technical analysis from Saylor, we cannot evaluate whether his opposition is based on sound cryptography or on balance sheet comfort. The silent guardian may be protecting us from a phantom.
Takeaway: The Discipline of Transparency
The outcome of this governance dispute will define Bitcoin's next decade. If Saylor publishes his 110 reasons and they withstand peer review, the network stays conservative. If he remains silent, the debate degenerates into a tug-of-war between money and code.
I do not know whether BIP-110 should pass. But I know that the community deserves more than 110 hidden bullet points. The ledger remembers everything. The narrative forgets the details. The discipline of transparency is the only way to ensure that the narrative does not overwrite the truth.
Protecting the user means trusting them with the full analysis. Not just a tweet about 110 reasons.