BIP-110: The Soft Fork That Could Split Bitcoin's Soul

The code compiles, but the reality bankrupts. BIP-110 claims to clean Bitcoin's house. It instead exposes a governance rot deeper than any spam transaction. BIP-110, proposed in mid-2025, is not your typical soft fork. It does two things: first, it caps arbitrary data per transaction at 34 bytes, effectively killing Ordinals inscriptions and most token protocols. Second, it lowers the activation threshold from 95% miner approval to just 55%. The author frames this as “restoring Bitcoin’s monetary purity.” The community smells a coup. I have audited enough smart contracts to know when a proposal bundles technical changes with rule changes. That is a red flag. BIP-110 does exactly that: it mixes a reasonable complaint (block space pollution from inscriptions) with a radical governance hack (lowering the consensus bar). Any responsible engineer would separate the two. They didn’t. That tells me the goal is not technical improvement — it is power reallocation. Let me walk through the mechanics. The 34-byte limit targets OP_RETURN and Taproot data fields. Currently, Ordinals use Taproot scripts to store entire files. BIP-110 would revert that by restricting new outputs from containing data beyond 34 bytes. Existing inscriptions become frozen — you can still own them, but you cannot spend or transfer them under the new rules. This is not cleanup; it is asset confiscation by protocol change. The effect is immediate on the Ordinals ecosystem: floor prices of major collections would drop 60-80% within a week. I saw that happen when I exposed the metadata randomization flaw in a PFP collection back in 2021. The same panic happens when users realize their “digital property” relies on a rule that can be changed by a handful of miners and nodes. The bigger issue is the 55% threshold. Bitcoin today uses 95% for soft forks precisely because it forces near-universal consensus. BIP-110’s author argues that 55% is enough because “miners are not the only stakeholders.” That sounds democratic, but it is a Trojan horse. At 55%, a majority of miners plus a coordinated node campaign (UASF) can force a rule change against the wishes of the rest of the network. I do not trust the audit; I trust the exploit. And the exploit here is the lowered threshold itself — a vulnerability, not a feature. Now, the technical reality: BIP-110 has a critical consensus bug discovered by Dathon Pwn, called BlockSlop. The bug means that nodes running the BIP-110 code will interpret old blocks differently than non-upgraded nodes, creating a permanent fork in the shared history. This is not a theoretical risk; it is a live vulnerability that would cause a chain split if activated. The fact that the proposal was published with such a flaw confirms what I already suspect: the author rushed the code to push the governance change before the technical review could catch it. The code compiles, but the reality bankrupts. Miner support is negligible. As of today (July 2025), only about 2% of miners have signaled support for BIP-110. Jameson Lopp and Michael Saylor have publicly opposed it. Lopp’s argument is that any restriction on data usage sets a precedent for censorship — once you draw a line at “spam,” who decides what counts as spam in the future? Saylor’s objection is more practical: the proposal would cripple the emerging Layer 2 ecosystem that relies on Taproot commitments for sidechains and state channels. Both arguments have merit, but the real killer is the lack of miner traction. If miners ignore it, the fork dies quietly. Yet the debate itself is damaging. The transaction is permanent; the mistake is not. The record of this discussion is now etched into Bitcoin’s social layer. Every proposal that tries to lower the bar will be compared to BIP-110. Even if this one fails, the idea that 95% is too high has been planted. That seed will grow. Contrarian angle: the bulls might say this proposal is healthy — it forces the community to explicitly reaffirm the 95% rule. They argue that any governance system must test its assumptions periodically. I concede that a cathartic debate can strengthen consensus. However, the BIP-110 proponents had better alternatives: they could have introduced a separate BIP to reduce block space with a separate threshold, or they could have started a research group on spam mitigation without touching governance. They chose the nuclear option. That suggests their true intent is to weaken the conservative consensus mechanism, not to clean the chain. Illusion has a price tag; truth has none. The illusion here is that BIP-110 is about reducing node load. The truth is it is about testing whether Bitcoin can be governed by a smaller, more activist subset. The market is not pricing this risk yet. If the proposal gains unexpected traction (say, a coordinated Twitter campaign by loud influencers), we could see a 5-10% dip in BTC price within hours. But the real damage is structural: every future upgrade will be haunted by the suspicion that someone wants to lower the bar. What happens next? By early August, miners will signal their final preference. If support stays below 5%, BIP-110 dies. If it somehow reaches 55%, we enter uncharted territory where the UASF (User-Activated Soft Fork) movement might try to bypass miners. That scenario would likely trigger a chain split, similar to Bitcoin Cash but with even less economic backing. The transaction is permanent; the mistake is not. My advice to anyone holding bitcoin: ignore the panic. Keep your private keys safe. If a UASF emerges, do not run any node software that is not signed by the Bitcoin Core project. The institution of Bitcoin is bigger than any one proposal. But monitor the signals: miner support rates, core developer statements, and the number of UASF-ready nodes. If the latter exceeds 10% of total reachable nodes, start hedging your portfolio with short-term options. For now, BIP-110 is a storm in a teacup. But every teacup holds the potential to spill. This proposal will be studied in crypto governance classes for years. It is a stress test of Bitcoin’s sociological firewall. The code compiles, but the reality bankrupts — only this time, the bankruptcy is not financial but consensual.