Surviving the noise to find the signal’s heartbeat
Over the past seven days, a single Bitcoin Improvement Proposal has consumed more developer attention than the last three BIPs combined. That proposal is BIP 110, a soft fork designed to cap transaction data size, enforce stricter limits on Taproot control blocks, and restrict undefined witness versions. On the surface, it is a technical housekeeping measure — a gentle nudge to curb bloat and protect node operators from rising costs. But beneath the surface, it has become a lightning rod, drawing the fire of Michael Saylor and exposing a fracture that runs through the very philosophy of Bitcoin governance. As I watch the debate unfold from my desk in Toronto, where I manage a portfolio of token fund investments, I am reminded of the ICO era, where technical proposals were often Trojan horses for deeper ideological agendas. BIP 110 is no different.
Where tokenomics meets the human condition
To understand the stakes, we must rewind. BIP 110 proposes to limit the size of script data in transactions, restrict Taproot control block signatures to a single variant, and ban undefined witness versions — effectively freezing any future script extensions without another fork. The activation threshold is set at 55% miner signaling, far below the historical 95% consensus standard that has protected Bitcoin from contentious changes. This low bar alone raises red flags. In my 2024 report "The Hollow Icon," I argued that decentralization is not just about hash distribution but about the diffusion of decision-making power. A threshold of 55% centralizes power in a slim majority of miners, opening the door for future proposals to bypass community consensus.
The debate has drawn heavyweight voices. Adam Back, the cypherpunk pioneer whose fingerprints are on Bitcoin’s earliest code, predicted the proposal would "stagnate within weeks" — a sign that even the technical elite see its foundation as weak. Michael Saylor, the corporate evangelist who has turned MicroStrategy into the largest public holder of Bitcoin, issued a forceful critique, calling the proposal a "coarse proxy for costs never measured" and warning it would sacrifice Bitcoin’s neutrality for a temporary, symbolic fix. Saylor’s stance is rooted in a strategic vision — one where Bitcoin remains the pristine settlement layer, free from the compromises of smart contract experimentation. But is he a guardian of neutrality, or an institutional investor protecting his balance sheet? The answer, I suspect, is both. And that duality is precisely what makes this narrative so rich.
Navigating the fog where logic meets faith
What makes BIP 110 a quintessential narrative trap is its packaging. The proposal bundles several unrelated restrictions into a single rule change, forcing the community to accept all or nothing. This is not just technical sloppiness; it is a governance tactic. By linking a relatively benign script size cap with a ban on future witness versions — which could be used for innovations like BitVM — the authors are leveraging the path of least resistance to shut down optionality. During my days auditing 42 whitepapers for a venture studio in 2017, I saw the same bundling strategy used to slide controversial clauses past distracted investors. The outcome was predictable: ugly surprises when projects failed to deliver. Here, the stakes are higher. If BIP 110 passes, Bitcoin will permanently lose the ability to add new computational capabilities without a future soft fork. That is a heavy price for a proposal that, as Saylor points out, addresses costs that have never been formally measured.
Let me drill into the technical specifics. The proposal limits script data to 10 kilobytes per input — a cap that, according to on-chain analysis of the last 12 months, would affect fewer than 0.5% of transactions. The median block size remains well below the existing 4MB limit, and the perceived "bloat" is concentrated in a handful of blocks during time-sensitive events. The authors of BIP 110 have not published a cost-benefit analysis, nor have they identified the specific nodes that would be saved from an existential DoS threat. Instead, they rely on a vague narrative that "something must be done" to protect the network’s weakest participants. This is reminiscent of the regulatory overreach we saw in DeFi in 2022 — rules based on fear rather than data. As a narrative hunter, I recognize this pattern: when the evidence is thin, the rhetoric thickens.
The restriction on undefined witness versions is even more troubling. Currently, Bitcoin’s witness structure allows for future script extensions without a consensus change — a flexibility that enabled the Taproot upgrade itself. By banning undefined witness versions, BIP 110 closes the door on innovations like BitVM, a technique that could enable Turing-complete computation on Bitcoin without a fork. BitVM is still in its infancy, but it represents a promising path for smart contract-like capabilities that preserve Bitcoin’s security model. To preemptively block that path is an act of profound shortsightedness. It is the equivalent of cutting down a forest because you worry about falling branches.
Unearthing value from the ruins of previous cycles
The contrarian angle here is that Saylor’s opposition, often framed as conservative resistance to change, is actually the most progressive stance. By blocking BIP 110, he is preserving the option space for future innovations. The paradox is that those who advocate for “protecting node operators” may end up harming them more in the long run. If Bitcoin becomes ossified, its value as a medium of exchange and store of value will eventually be challenged by more adaptable networks. The node operators who survive the short-term cost of data bloat will be the ones who reap the rewards of a network that continues to evolve.
Moreover, the controversy serves a healthy purpose. It forces the community to openly debate governance processes that have been taken for granted. The “code is law” ideal is being stress-tested by a political reality where a few influential voices can shape the agenda. Silence would be worse. As I learned during the DeFi Summer, when we assumed protocols were neutral, we ignored the human biases embedded in their design. BIP 110 forces us to confront that bias head-on. The real blind spot is the assumption that “more restrictions” equal “more security.” In a system built on permissionless participation, restrictions inevitably create incentives for circumvention. If BIP 110 passes, we might see a rise in off-chain data commitments or alternative scripting methods that undermine the very goals of simplicity and auditability. The law of unintended consequences applies doubly to protocol upgrades.
The low activation threshold of 55% is a ticking time bomb. If passed, it sets a precedent that a slim majority of miners can impose disruptive rule changes on the remaining nodes. This could lead to a scenario where a cartel of large mining pools overrides the objections of user nodes and developers. We have seen this pattern before — in the 2017 SegWit activation debate, where a similar low threshold was proposed but ultimately rejected in favor of a UASF (User-Activated Soft Fork) that achieved near-unanimous support. The community learned then that governance by brute force erodes trust. BIP 110 risks repeating that mistake, but with the added danger of locking in future innovation constraints.
From a market perspective, the impact is subtle but real. In a sideways market, chop is for positioning. This controversy does not directly affect Bitcoin’s price in the short term — it is too abstract for most traders. But for institutional investors, it whispers a question: Can Bitcoin govern itself without breaking into factions? If the answer is uncertain, those investors will hesitate to allocate more capital. I have advised hedge funds on framing strategies for conservative capital, and the message is clear: stability, predictability, and neutrality are the assets they seek. BIP 110 undermines all three.
The quiet architecture of decentralized trust
Where to from here? The BIP 110 controversy will not be resolved by a miner vote alone. The broader community of node operators, developers, and users must signal their rejection of such packaging tactics. The next narrative will likely be about “governance hygiene” — the establishment of clear rules for when and how soft forks can be bundled. Bitcoin’s value proposition as digital gold depends on its predictability and immutability. But predictability does not mean stagnation. The art lies in evolving without breaking the social contract.
I see two possible outcomes. First, the proposal fades as Adam Back predicted, with miners refusing to signal support and the one-year expiry clause rendering it moot. This outcome reinforces the status quo and strengthens the narrative of community self-correction. Second, the proposal gains unexpected traction, either through a coordinated miner push or a shift in developer sentiment. In that case, a counter-proposal will likely emerge — one that separates the script size cap from the witness version ban, allowing the former as a modest protection measure while preserving the latter for future innovation. I would bet on the first outcome, but I have been wrong before. In 2021, I warned my fund against over-leveraging on speculative NFTs, and we missed a 3x surge before the crash. The lesson was that narratives can defy logic for longer than expected.
Bitcoin’s silent architecture of trust is being tested. Will it remain the unchanging monument, or will it find a way to evolve without breaking its soul? I cannot answer that, but I can point to the signal: the noise over BIP 110 is a healthy sign that the community is still awake, still arguing, still alive. The worst fate for Bitcoin would be apathy. This debate, however messy, proves that the heartbeat of decentralization still pulses.