On August 1st, a window opens. Not for a new moon, but for a software-enforced schism. BIP-110, a proposal to amputate Bitcoin's data storage capabilities, will begin its forced activation phase. The numbers are stark: fewer than 1% of mined blocks carry a signal of support. Yet the code will proceed regardless. This is not democracy. This is a coup by consensus layer fiat. Execution is final; intention is merely metadata. The market has priced this as a non-event. It is not.
Bitcoin is facing its deepest governance rift since the SegWit civil war. At stake is the network’s identity: a pure digital cash system or a decentralized data layer that hosts NFTs, tokens, and metadata. Ordinals and BRC-20 have proven that users are willing to pay serious fees for non-transfer functions—Runes alone drove a 32% fee spike in October 2024. BIP-110 aims to stop this by limiting non-standard data outputs (like OP_RETURN) to 256 bytes, effectively killing large inscriptions. The proponents, led by Dathon Ohm and Luke Dashjr, argue that storing arbitrary data turns full nodes into unpaid archives, bloating the UTXO set and increasing long-term costs. The opponents, including Ordinals creator Casey Rodarmor, see this as a censorship of use cases that brought new life to the network.
The Technical Mechanism of BIP-110 BIP-110 is a soft fork that adds a new consensus rule: any transaction with more than 256 bytes of non-standard data in its OP_RETURN or witness is invalid. Nodes running BIP-110 will reject blocks containing such transactions, even if those blocks are valid under the old rules. The activation is forced—after a one-year waiting period (the window opens Aug 1), any node that has upgraded will enforce the rule, regardless of the mining hashrate supporting it. This is the most aggressive activation mechanism Bitcoin has seen outside of emergency patches. Based on my audit experience with protocol-level changes, this creates a unique risk: a chain split where a minority of hashrate (the <1% miners) produces blocks that the upgraded nodes accept, while the majority continues on the old chain. Blockchain inheritance is a feature until it becomes a trap.
The Ordinals Bypass Scheme Casey Rodarmor has already proposed a workaround: split large inscription files into 256-byte chunks, each placed in its own transaction. Each chunk is compliant with BIP-110’s limit. The scheme has been approved by the author and is being tested. On the surface, this preserves Ordinals. But dig deeper. A single 100KB inscription becomes ~400 transactions. This is not a reduction—it is an explosion of UTXO count. The network will see a flood of tiny outputs, each costing a fee. The total data stored per byte remains similar, but the block space consumed per byte of actual data increases dramatically. The very problem BIP-110’s supporters cite—spam and UTXO bloat—will be amplified. The bypass turns a clean inscription into a fragmented chain of dependencies. Inheritance is a feature until it becomes a trap. Forks happen. Code remains.
The Activation Mechanism as Governance Bug BIP-110’s forced activation bypasses the traditional requirement for majority hashrate support. This is not a bug in the code—it is a bug in the governance model. Bitcoin’s “rough consensus” relies on miners voting with their hashrate. Here, a small group of core developers and node operators are imposing a rule through software fiat. Luke Dashjr’s statement— “If BIP-110 fails, Bitcoin will fail too”—reveals an absolutist ideology that sees any deviation from the pure digital cash vision as existential. But the market already spoke: Ordinals and Runes added real fee revenue to miners. The 1% support rate is a clear economic signal. Yet the code will execute. This is a principal-agent problem: the developers who write the code are not the same as the economic actors who secure it. Execution is final; intention is merely metadata.
Security Blind Spots The bypass scheme is unaudited. It introduces new script patterns that could create malleability or reentrancy-like risks (though reentrancy is more an EVM concept, analogous state-dependent issues exist). More critically, the forced activation could trigger a classic chain fork. If the BIP-110 chain (let’s call it the Covenants Chain) produces empty blocks because 99% of hashrate rejects it, it will stall. But exchanges and wallets may still label it as “Bitcoin” if they run the upgraded nodes. Users could see two Bitcoin tickers. Replay attacks become possible. From my forensic work on the ETC hard fork, I know that a split is never clean. The shadow chain lingers, confusing custodians and exchanges. The market is underestimating the operational chaos.
Contrarian: BIP-110 May Cement Ordinals’ Permanence The expected narrative is that BIP-110 will kill Ordinals. But consider a different path: if the Covenants Chain fails to attract any mining power, it becomes a dead chain. The original chain continues, Ordinals thrive, and the bypass scheme makes them even more persistent. The forced activation, by failing to achieve consensus, could actually entrench the very activity it sought to eliminate. Furthermore, the bypass scheme will make the original chain more congested, driving up fees and encouraging L2 solutions like Lightning or Stacks for high-throughput applications. The real winner may be competing L1s like Ethereum or Solana, which offer cheaper data storage. Bitcoin’s attempt to purify itself might push its most innovative users away.
Macro-Technical Synthesis This is not just a technical debate; it is a renegotiation of Bitcoin’s value proposition. The original whitepaper describes a peer-to-peer electronic cash system. Decades later, the network has evolved into a store of value with a thriving ecosystem of digital artifacts. BIP-110 represents a regression to the mean—a forced return to the original narrow use case. But economic history shows that networks that resist user demand for new functionality often lose relevance (see AOL vs. the open web). The mining community, by voting with such low support, has implicitly endorsed the expansion of use cases. Their self-interest is aligned with transaction fees. A BIP-110-induced reduction in fee income would make miners more dependent on block subsidies, which are halving every four years. This is a slow-burn security budget crisis.
Takeaway The August window is not an end, but a beginning. We are entering a period where Bitcoin’s governance is tested under fire. The market is pricing this as a 1% event. It is not. The true risk is not the activation itself, but the fragmentation of trust. If a minority can force a rule change through software fiat, what prevents the next ideological battle? The answer will be written not in code, but in hashrate distribution and the decisions of exchanges. Watch the hash rate on the Covenants Chain after August 1. If it stays below 1%, the fork is dead. If it climbs, we have a war on two fronts. Reentrancy is still the ghost in the machine—but this time, the ghost is governance.