Saylor’s BIP-110 Stance Fuels Bitcoin Feud as Miner Support Stalls
Michael Saylor’s attack on BIP-110 supporters, summed up in his line “Don’t fix what’s not broken,” has kicked off an ugly fight inside the Bitcoin community. Some traders blame the dispute for making an already nervous market even jumpier. My take: calling this merely a code disagreement misses the point. The real questions are who gets to change Bitcoin, when intervention is justified, and what happens when major holders turn on each other in public. Bitcoin’s fall below $64,000 made that last question feel a lot less academic. The mood changed fast.
On July 27, Saylor sharpened his criticism of BIP-110, a proposed Bitcoin soft fork. The Strategy founder portrayed its supporters as newcomers meddling with a system that works. His position is blunt: changes to Bitcoin’s main protocol should be rare and cautious. They also need a convincing case. He does not think BIP-110 clears that bar. Fair enough—but caution is still a choice, not a neutral position.
BIP-110, formally named the “Reduced Data Temporary Soft Fork,” may be Bitcoin’s most bitterly contested proposal of 2026. It would temporarily restrict how much data transactions can carry. Why does that matter? Because supporters believe the restriction would reduce network spam and slow Ordinals-style inscriptions. They do not want Bitcoin filling up with the sort of memecoin traffic associated with Solana. Saylor and Blockstream co-founder Adam Back remain unconvinced; both oppose making repeated changes to Bitcoin’s base code. Most summaries stop there. That is only half right. Critics have raised a more serious concern: the proposal could leave some older BTC addresses open to theft. That remains a disputed claim, not an established fact.
The fight exposes an old Bitcoin problem: how do you improve a network when its stubborn resistance to change is part of the appeal? It sounds like developer-forum material—until the price starts falling. Then nobody can ignore it. Saylor controls a large BTC position through Strategy and helped move corporate Bitcoin buying from a fringe bet into boardroom discussions. Investors listen when he attacks a protocol proposal, even if his comments alone did not cause the selloff. I’ll be honest: assigning a clean cause to a Bitcoin move is usually too convenient. Still, a public feud can rattle a market that was nervous already. After BTC dropped below $64,000, Pierre Rochard, a former vice president of research at miner Riot Platforms, put it more starkly: “BIP-110 FUD is causing Bitcoin to crash.” That is his read on the market, not proof of cause and effect. It captures the mood.
Saylor’s comments drew an immediate response. Paul Sztorc, one of the soft fork’s most vocal supporters, called him a “hypocrite.” Sztorc noted that Saylor was no early Bitcoin convert and accused him of bringing his own “terrible ideas” into the community. The history is awkward. Saylor dismissed Bitcoin in 2012, using language often compared with Peter Schiff’s criticism, before changing his mind and becoming one of its loudest champions. He later created a Bitcoin Security Consortium with Coinbase and BlackRock to improve the network’s defenses. Counter to the usual advice, that reversal does not automatically weaken his argument; people are allowed to change their minds. None of it proves whether he is right about BIP-110. It does explain why the dispute became personal so quickly. This is about code. It is also about status and who, exactly, has earned a say in Bitcoin’s next move.
For traders, miner signaling is the figure to watch. Only 2.3% of miners currently support BIP-110. It needs 55% before the August 9 deadline. The gap is enormous. Weak support makes activation unlikely, but an attempted upgrade without broad agreement could briefly split the network. Is that overkill as a concern? No, because exchanges might suspend BTC deposits and withdrawals while choosing which chain to recognize and updating their systems. Those pauses could drain liquidity at a particularly bad moment, adding pressure to the price. Traders need dependable settlement. A chain dispute undermines it. In my view, BIP-110 is a sharp example of how an argument buried in developer forums can land, almost overnight, on a trading screen.
What this means
Bitcoin users are increasingly divided over transaction data and the network’s growth. One camp treats strict limits and reluctance to change as safeguards. The other argues that Bitcoin has to respond when uses such as Ordinals consume block space in ways earlier users never expected. Both concerns are real. Yes, that sounds frustratingly balanced, but pretending one side has no case would be worse. For traders, the immediate problem is uncertainty while miners, Saylor, Adam Back, and BIP-110 supporters fight in public. BTC’s slide below $64,000 does not prove BIP-110 caused the drop. Markets rarely hand us explanations that clean. Still, I would not dismiss the timing: it shows how quickly a technical disagreement can become part of the price narrative.
August 9 is the next date to watch. If miner support remains below 55%, BIP-110 probably will not activate, removing one immediate uncertainty. A sudden rise in support changes the picture. It could revive fears of a chain split and push exchanges to prepare for temporary transaction freezes. What should traders track? The miner percentage first, then fresh comments from Saylor, Adam Back, and BIP-110 supporters. The number matters more than the noise. Then again, dismissing the noise entirely would be a mistake; a sharp swing in miner backing or public sentiment could move BTC again. My take: watch closely, but do not act as though anyone knows where the price is headed. Nobody does.