Michael Saylor doesn't issue warnings lightly. When he publicly declared BIP 110 a 'true negative' for Bitcoin, the market barely blinked. But I did. Because when a $25B institutional holder challenges a proposal that claims to solve a problem nobody measured, you ask questions. I didn't need a whitepaper to see that something was off.
Context. BIP 110 is a Bitcoin Improvement Proposal that bundles three distinct constraints: a limit on script size, a cap on Taproot control block size, and an outright ban on undefined witness versions. The stated goal is to reduce data bloat and shrink the DoS attack surface. Presented as a soft fork, it carries a low activation threshold of 55% miner signaling, far below the traditional 95%. The authors argue that this protects node operators from rising costs and keeps fees low. But the proposal’s timing and packaging raise immediate red flags.
Core Technical Analysis. Let’s cut through the noise. The proposal lacks empirical justification. Where is the data proving that script size is creating a measurable cost to nodes? Saylor called it a 'rough proxy for a cost that was never measured.' He's right. In my 23 years trading and building on these networks, I’ve learned that any constraint introduced without concrete evidence is a gamble. Worse, BIP 110 bundles three unrelated limits into one vote. This is classic governance gaming — pass one contentious rule by tying it to two that seem benign. I’ve seen this playbook before in 2017 when exchanges pushed API limit changes disguised as 'optimizations'.
The 55% signal threshold is the most dangerous part. Bitcoin’s governance has historically relied on near-universal consensus (95%) to avoid exactly this kind of dispute. Lowering the bar opens the door for future proposals to be rammed through by a coalition of large miners, undermining the 'one node, one vote' ideal. The authors claim this prevents a single mining pool from blocking progress, but it actually hands more power to the largest pools.
Now the real killer: BitVM. This proposal — still in research stage — would allow Turing-complete computation on Bitcoin without changing the consensus layer. It could unlock decentralized bridges, financial derivatives, and complex smart contracts, all secured by Bitcoin’s hash power. BIP 110 would effectively kill BitVM before it’s born. By restricting script size and committing to zero tolerances, it preemptively closes the door on any future use of Bitcoin script for computation. This is not about reducing DoS. This is about choosing between Bitcoin as a static store of value and Bitcoin as a platform for innovation.
From my own experience — running automated arbitrage bots in 2017 taught me that infrastructure decisions have compounding effects. The smallest restriction today becomes a brick wall tomorrow. I saw this with Poloniex’s API rate limits; they squeezed profitable strategies and drove liquidity to alternatives. Bitcoin cannot afford to sacrifice optionality at this stage of its evolution.
Contrarian Angle. The mainstream narrative frames BIP 110 as a necessary clean-up: protect nodes, keep fees low, simplify the protocol. But the counter-intuitive truth is that passing BIP 110 would be the biggest threat to Bitcoin’s long-term value proposition. Institutional investors like MicroStrategy don't buy Bitcoin purely as a hedge; they buy into the narrative that Bitcoin can evolve to meet new demands. If the network signals that it will proactively close off future use cases, that narrative breaks. Saylor isn’t just protecting his balance sheet — he’s defending the 'innovation optionality' that makes Bitcoin attractive as a store of value for the next century.
Another blind spot: the assumption that low fees are inherently good. In a bull market, high fees drive demand for Layer 2 solutions, which in turn expand the ecosystem. Artificially capping script size may lower fees in the short term, but it starves the fee market that should sustainably fund miner revenue after the last Bitcoin is mined. This proposal is a short-term fix for a long-term systemic need.
The numbers don't lie. Look at the on-chain data: the alleged 'data bloat' is minimal. The average script size hasn’t increased dramatically since Taproot. The proposal is solving a phantom menace.
Takeaway. BIP 110 will likely fail to activate. Adam Back predicts it will stall within weeks. But the debate is a stress test for Bitcoin’s governance. It reveals a growing schism between 'maximalists' who want Bitcoin to remain a stateless asset with minimal features, and 'evolutionists' who see it as the foundation for a new financial system. For traders, this is noise — <b>unless it triggers a price dislocation</b>. Watch the miner signaling on BIP 110. If it crosses 55%, the risk premium on Bitcoin should widen. If it fails (as I expect), it's a buy signal for Bitcoin’s adaptive capacity.
This is the part where everyone gets excited, and I start selling — but only if the proposal looks likely to pass. Right now, the market is underestimating the consequences of a successful activation. Stay nimble, check the chain, and never trust a bundled fix without independent verification.