BIP 110: The Soft Fork That Wants to Cap Bitcoin's Potential

The activation threshold is 55%. Not 95%. Not even 75%. Just a simple majority of miner hash power to push through a soft fork that rewrites Bitcoin's transaction rules. That is the first red flag. Code does not lie, but liquidity does. And this proposal is bleeding liquidity from the future of Bitcoin's innovation pipeline. Michael Saylor, founder of MicroStrategy and the largest single corporate holder of Bitcoin, did not mince words. He called BIP 110 a "crude proxy" for an unmeasured cost. He warned it would break the neutrality of the protocol. Adam Back, CEO of Blockstream and a core developer whose name is etched into Bitcoin's history, predicted the proposal would stall within weeks. When the two most influential voices in Bitcoin publicly oppose a technical change, you don't ignore it. You audit the code. BIP 110 is a soft fork designed to reduce the size of certain transactions and limit future witness versions. On the surface, it aims to lower block data bloat and mitigate denial-of-service attacks. But peel back the engineering layers and you find a bundle of unrelated restrictions: capping script sizes, freezing undefined witness versions, and locking the Taproot control block. It is a shotgun approach to protocol maintenance. I have seen this before. In 2017, I audited the Parity multisig library and spotted a delegatecall vulnerability that could drain millions. The team had bundled multiple changes into a single upgrade without isolating risk. The result was a $31 million loss. BIP 110 makes the same mistake. The technical analysis reveals a proposal built on shaky assumptions. The cost it claims to address—node operator storage burden—was never measured. The solution is a set of arbitrary limits that will become permanent once activated. Soft forks are backward-compatible, but they still lock the network into a specific rule set. This one would block future upgrades like BitVM, which relies on using the witness data for off-chain computation. BitVM is Bitcoin's best shot at enabling smart contracts without changing the base layer. BIP 110 closes that door without a discussion. The moon is a myth; the ledger is the only truth. And this ledger would be permanently censored. From a governance perspective, the 55% activation threshold is a departure from Bitcoin's tradition of supermajority consensus. Historically, soft forks required 95% miner approval to ensure community alignment. Lowering the bar to a simple majority opens the door for minority-driven rule changes. Saylor framed this as a neutrality violation: "Bitcoin should not pick winners among future technologies." I agree. The protocol must remain a passive verification engine, not an active gatekeeper. Trust the math, ignore the memes. The math here says a bare majority can impose long-term constraints. Now the contrarian angle. The mainstream narrative paints BIP 110 as a defensive measure against spam attacks. Proponents argue that limiting transaction size protects node runners and keeps fees low. But let me test that logic against the data. Over the past 12 months, Bitcoin's average block size remained well below the SegWit cap. The DoS risk is theoretical, not empirical. Meanwhile, BitVM is moving toward a testnet launch. Its success depends on holding flexible witness space. By restricting that space now, BIP 110 essentially taxes future innovation to solve a problem that hasn't materialized. Survival is the first profit metric. But survival of what? A stagnant L1 that cannot adapt, or a vibrant ecosystem that grows? The contrarian truth is that BIP 110 is not about security. It is about control. The architects of this proposal want Bitcoin to remain a simple store of value, not a platform. They fear the complexity of smart contracts and the regulatory scrutiny that comes with them. But markets punish inflexibility. Every Layer2 solution from Lightning to BitVM adds value to Bitcoin as the settlement layer. Killing off that potential reduces Bitcoin's competitive edge against programmable L1s like Ethereum or Solana. Let me share a personal experience. In 2020, when Uniswap V2 launched, I front-ran the event using a Python script that monitored the contract deployment timestamps. I bought into the ETH/USDC pool seconds before public trading began. The profit was immediate: 15% arbitrage. That trade worked because I understood the code latency and the data flow. Speed kills, but patience compounds. BIP 110 is the opposite of patience. It is a rushed, reactionary patch disguised as progress. The market will not reward it. What happens next? The proposal has a one-year expiry. If miners signal support at the 55% threshold, the activation window opens. But I expect the opposite. The combined weight of Saylor, Back, and the broader developer community will kill it through non-adoption. Bitcoin's governance is messy, but it self-corrects when outliers try to force change. The signal we should watch is the number of public rejections from node operators. If that crosses a critical mass, BIP 110 becomes a dead letter. Takeaway: Do not mistake noise for signal. BIP 110 is a political maneuver dressed as a technical upgrade. It will fail, but the scars on Bitcoin's governance model will remain. The 55% threshold precedent, if left unchallenged, could be reused by future proposals. Every activist should scrutinize every future BIP activation threshold. That is where the real battle is fought. Trust the math, ignore the memes. The math says 55% is too low for a permanent rule change.