Bitcoin's Governance Crossroads: Why BIP 110 Could Be a Defining Moment for Neutrality and Innovation

The bear market didn't kill Bitcoin's spirit; it gave us the quiet to hear the internal debates. Last week, as BTC hovered around $65k, a seemingly technical proposal—BIP 110—ignited a firestorm. Michael Saylor, the man who turned MicroStrategy into a Bitcoin treasury, called it a 'crude proxy' for an unmeasured cost. He wasn't attacking the code; he was defending a philosophy. The proposal aims to limit certain transaction outputs to reduce data bloat. But behind the technical jargon lies a profound question: Should Bitcoin remain a neutral settlement layer, or concede to pragmatic limits that might strangle future innovation? To understand the stakes, we need to look at what BIP 110 actually proposes. It's a soft fork that would restrict script size to ≤100 bytes, limit Taproot control blocks, and prohibit undefined witness versions. The author argues this lowers nodes' exposure to DoS attacks and curbs data growth. On paper, it sounds reasonable—a conservative tweak. But the devil is in the aggregation. The proposal bundles multiple, unrelated restrictions into one package, making it impossible to consider each on its own merit. This 'bundling' is a governance tactic that Saylor rightly flagged as a threat to neutrality. He wrote on X that the proposal 'sacrifices neutrality for a temporary, symbolic solution.' Adam Back, the Blockstream CEO, predicted it would 'stall in weeks'—a clear signal of its weak community footing. The activation threshold amplifies the controversy. BIP 110 requires only 55% miner signaling, far below the 95% traditionally needed for Bitcoin soft forks. This lower bar could allow a minority of miners to push through a contentious change, undermining the principle of broad consensus. It's a governance innovation that some see as agile and others as reckless. Saylor's critique cuts deeper: he argues that the proposal fails the 'neutrality test.' A neutral protocol should not pre-judge transaction types—whether Taproot scripts or future witness versions—as harmful. By restricting them, BIP 110 imposes a value judgment on how users should interact with the chain. This is where the core insight emerges. The proposal is not just about data limits; it's about closing off future possibilities. Bitcoin's innovation path depends on experimental features like BitVM, which rely on large scripts and undefined witness versions. BIP 110 would effectively ban those experiments before they even begin. I've seen this pattern before. In 2017, as a 20-year-old computer science student in Nairobi, I traced the reentrancy vulnerability in The DAO hack for 150 hours. That taught me that code is law, but flawed by human hubris. The DAO's failure wasn't because the idea was wrong; it was because we didn't leave room for iteration. Bitcoin's strength has always been its evolutionary capacity—Taproot itself was a leap forward in smart contract privacy. To now lock the door on future leaps is a betrayal of that spirit. About Me: In 2020, I forked Curve's stableswap to understand impermanent loss. That experience showed me that the most elegant solutions are those that leave room for future discovery. Curve's invariant was beautiful precisely because it allowed for multiple asset pairs within a single pool—it was an architecture of optionality. BIP 110 does the opposite: it constrains the canvas. The same year, I wrote 'The Poetry of Liquidity,' arguing that yield farming was not gambling but participation in a new economic layer. That metaphor applies here: BIP 110 is like censoring certain stanzas from the poem before it's written. We don't know what poetry the unused witness versions might produce. Closing them off is an act of intellectual cowardice. From a technical perspective, the proposal's effectiveness is questionable. As Saylor pointed out, it targets inputs that have never been quantified as a cost. The data bloat problem is real, but BIP 110's approach is symbolic at best. The real driver of UTXO growth is the influx of spam and low-value transactions, which are already cheap. Limiting script size won't stop that. A more surgical approach would be to increase the cost of certain operations via fee adjustments or to incentivize node operators through better tooling. But those are harder to implement. BIP 110 is the low-hanging fruit—a quick fix that feels good but does little. The contrarian view deserves a moment in the light. Some argue that BIP 110 is a reasonable precaution. Unbounded data is a real risk for node operators, especially those running full archival nodes. The proposal could prevent a worst-case scenario where a single attacker floods the network with massive transactions, grinding the system to a halt. The 55% threshold, while low, could allow grassroots activation without the deadlock of supermajority politics. Maybe Saylor's opposition is self-serving because MicroStrategy's BitVM plans are a long shot—perhaps even a distraction from Bitcoin's primary role as digital gold. If Bitcoin is to remain secure, it must prioritize simplicity over flexibility. But I find this argument insufficient. Simplicity should not come at the cost of adaptability. The history of protocol design shows that flexibility often trumps rigidity. Consider the TCP/IP protocol suite—its layered architecture allowed the internet to evolve from simple email to streaming video. Bitcoin needs similar layering. BIP 110's restrictions would fracture that layering, forcing innovation to occur off-chain in ways that could weaken security. The bear market didn't break us; it gave us the space to ask: What kind of Bitcoin do we want to build? The answer should be one that remains open to the unknown. We don't need to fear proposals; we need to fear silence. The debate around BIP 110 is healthy because it forces the community to articulate its principles. Saylor's stance is a defense of those principles—that neutrality means not picking winners or losers among transaction types. The fact that a proposal with such weak technical backing can cause such a stir is a testament to Bitcoin's living governance. But the risk remains: if the proposal somehow passes, it could set a precedent for future restrictions. The 55% threshold could become a tool for powerful miners to impose their will on the rest of the ecosystem. That would be a blow to Bitcoin's credibility as decentralized money. Looking forward, the most likely outcome is that BIP 110 stalls, as Adam Back predicted. The community will reject it not because it's dangerous, but because it's unnecessary. However, the conversation leaves a residue. It reminds us that governance is not just about code—it's about narratives. The narrative of neutrality versus pragmatism will continue to shape Bitcoin's evolution. The next proposal might be smarter, framed as a security improvement rather than a restriction. The community must remain vigilant against creeping centralization, whether through code or consensus. The takeaway is clear: Bitcoin's resilience lies not in coding, but in its ability to argue about its soul. This proposal will likely fade, but the conversation will resonate. The bear market didn't break us; it gave us the space to ask: What kind of Bitcoin do we want to build? I'll be watching, notebook in hand, curious and hopeful.