In the quiet aftermath of the 2022 crash, Bitcoin's community faces a more subtle battle than the usual cycle of boom and bust. This is not a debate about price, but about the fundamental architecture of trust. A new proposal, BIP 110, has surfaced, aiming to cap certain transaction attributes to reduce data bloat and potential denial-of-service vectors. On its surface, it reads as a prudent, conservative measure. Yet, the reaction has been anything but calm. Michael Saylor, the most prominent institutional holder of Bitcoin, has publicly denounced it as a 'rough proxy for a cost that was never measured,' and a violation of the protocol's sacred neutrality. This is not a technical squabble; it is a schism that reveals the fragile foundation upon which Bitcoin's future rests.
BIP 110 is a soft fork proposal that seeks to limit the size of scripts, restrict Taproot control blocks, and effectively freeze the use of undefined witness versions. The stated goal is to protect node operators from rising costs and to prevent transaction-relay attacks that could bloat the blockchain. The proposal has reached a 'Complete' status in the BIP process, but it has not achieved consensus. Its activation mechanism is unusually aggressive: a miner signal threshold of just 55% over a difficulty period, far lower than the historical standard of around 95% for contentious upgrades. This low bar is itself a source of contention, as it opens the door for a minority of hash power to force through a rule change that a majority of the community may reject.
Beyond the façade of technical optimization, BIP 110 carries a heavy philosophical weight. It bundles three separate restrictions into one package: script size, Taproot control block size, and the prohibition of new witness versions. This packaging is a classic governance maneuver. Based on my experience auditing protocol proposals, bundling disparate restrictions often masks a lack of rigorous individual justification for each. The author avoids the hard work of proving each limit's necessity by presenting them as a single, unified 'problem.' This is where the core of the conflict lies. The proposal implicitly argues that the cost of future flexibility is too high—that the risk of a theoretical DoS attack outweighs the potential of as-yet-uninvented applications. This is an argument for stagnation disguised as security.
The most critical impact of BIP 110 is not on current Bitcoin users, but on the entire trajectory of the network's evolution. The proposal explicitly closes the door on technologies like BitVM, which promise to bring sophisticated computation to Bitcoin without altering its base layer. BitVM is not a trivial experiment; it represents a pathway for Bitcoin to host complex smart contracts, cross-chain bridges, and verifiable compute markets. By capping script sizes and limiting witness versions, BIP 110 would make BitVM economically unviable. It is akin to a nation building a high-speed rail network but then capping the speed of every train to 30 miles per hour out of fear of a derailment. The irony is that Bitcoin's value as a resilient, neutral settlement layer derives from its ability to be a foundation for innovation, not a walled garden. Fragility is the price of unsecured innovation, but BIP 110 trades that fragile potential for an illusion of stability.
The contrarian angle here is that the debate is not really about data limits or DoS prevention. Those are technical proxies for a deeper conflict: the tension between Bitcoin as a simple store of value and Bitcoin as a programmable base layer. Saylor's opposition is not merely technical; it is a defense of the institutional narrative. A Bitcoin that evolves unpredictably, that opens itself to complex computation, poses a perceived risk to its status as a 'digital gold' suitable for corporate treasuries. Large holders prefer a stable, predictable asset. BIP 110, ironically, serves that narrative by killing future innovations that might introduce unknown risks. Yet, Saylor himself opposes it, calling it a violation of neutrality. This exposes a paradox: even the most vocal advocates of Bitcoin's immutability are drawing lines in the sand about what changes are acceptable. When the flow stops, we see what truly holds—and what holds here is not consensus, but the power of a few loud voices.
The takeaway is uncomfortable. The silence from the broader market suggests investors are not pricing in this governance risk. They should be. The real danger is not that BIP 110 passes; it is that the process itself becomes a mechanism for entrenching a narrow vision of Bitcoin's future. The proposal may stall, as Adam Back predicts, but the precedent of a low-signal threshold and the bundling of unrelated rules has been set. This is a warning signal for anyone who believes Bitcoin's governance is inherently stable. In the quiet aftermath, only the resilient remain—and resilience here requires not just strong code, but a community willing to defend the network's potential against the guardians who fear it.