Miner support for BIP-110 sits below 1%. The forced activation window opens in four weeks. These two facts contradict every norm of Bitcoin governance. The protocol that prides itself on rough consensus is about to be torn apart by a rule change that the vast majority of its own economic majority rejects. This is not a debate about technical merit. This is a coup attempt by a minority of core developers who believe they know better than the market what Bitcoin should be.
Context
Ordinals and Runes turned Bitcoin into a data layer. Since early 2023, users have inscribed images, texts, and even full applications onto satoshis, paying millions in fees to miners. Runes, a fungible token protocol, boosted miner fee revenue by 32% in October 2024. This new use case directly challenged the original 'digital cash' vision. A contingent of developers, led by Luke Dashjr, saw this as spam. Their solution: BIP-110, which would cap non-financial data per transaction at 256 bytes — effectively killing Inscriptions. The proposal is already implemented in Bitcoin Knots. But miners are not voting for it. The signal is clear: they prefer the fees. Yet the code contains a forced activation mechanism: no matter what miners do, starting August 8, nodes running Bitcoin Knots will reject any block containing oversized OP_RETURN data if a supermajority (75%) of blocks in the previous period are not flagged. This is the ticking time bomb.
Core: A Forensics of the Governance Failure
The forced activation clause is not a technical workaround. It is a declaration of war. Bitcoin’s governance has always relied on economic majority: miners signal, full nodes follow, and the chain that pays the most is the real Bitcoin. BIP-110 bypasses this entirely. It says: 'We, the software gatekeepers, will enforce the rule regardless of what miners want.' This is not a soft fork in any meaningful sense. It is a minority enforcement that, if executed, will produce a chain split.
From my 2018 deep dive into the 0x v2 audit, I learned that every protocol change creates a power asymmetry. Here, the asymmetry is between the code authors and the network participants. The drafters of BIP-110 control the default client. They know that a forced activation, even with negligible miner support, can force the remaining nodes to choose: accept the new chain or stay on the legacy chain. The legacy chain will have no Inscriptions either, because the miner set that stays will still create blocks that are rejected by BIP-110 nodes. The result will be two Bitcoin blockchains: one 'Core Chain' following the existing rules (with Inscriptions still legal), and a 'Covenants Chain' running BIP-110. Both will claim to be the real Bitcoin. History shows that such splits are damaging: the Bitcoin Cash fork in 2017 showed that value is not preserved equally. But at least BCH had near-unanimous miner support. Here, the supporter is a small group of ideological core developers.
What about the Ordinals side? Casey Rodarmor and lifofifoX have proposed a workaround: split each Inscription into 256-byte chunks that comply with the OP_RETURN limit. This is technically clever but operationally disastrous. A single 400-kilobyte image would require over 1,500 transactions. The network would be flooded with tiny UTXOs, each paying a fee. The total transaction count would explode, defeating any argument about reducing spam. Worse, this workaround is not audited. No formal security review has been conducted. The code may contain integer overflow or logic errors. High yield is a warning, not a welcome. The same applies to high-complexity workarounds.
The real issue is 'block space rent.' Bitcoin’s fee market historically prices security by demand for settlement. Ordinals demonstrated that there is enormous latent demand for data storage. BIP-110 supporters consider this a form of rent extraction that harms users, but the data tells a different story. In 2024, mining revenue from fees peaked at over 30% of total block reward due to Runes. Miners are profit-maximizing agents. When 99% of miners reject a rule change, the market is signaling that the current allocation of block space is efficient. BIP-110 is an attempt to override market efficiency with developer ideology. Code does not lie; people do. The code of BIP-110 will lie about what the market wants.
Contrarian: What the Bulls Got Right
It is tempting to label BIP-110 supporters as anti-innovation Luddites. But they have one defensible point: permanent data bloat on Bitcoin is a form of externalities. Full node operators who validate transactions must store all data forever. Inscriptions, especially large ones, increase the cost of running a full node. Over time, this could centralize validation to entities with more storage, contradicting Bitcoin's core promise. The bulls of the Ordinals ecosystem have not adequately addressed this. They argue that storage is cheap, but that is a short-term view. As the UTXO set grows, pruning becomes less effective, and the cost of a full node rises. If the cost exceeds even moderate household budgets, we end up with two tiers: light clients and professional nodes. That is centralization by economics.
Another counterintuitive insight: a BIP-110 enforced split might actually save Bitcoin's original vision. If the Covenant Chain gains enough traction (unlikely but possible), it would serve as the pure digital cash layer. The Core Chain would continue as the data-rich, fee-heavy version. The market would decide which chain holds the Bitcoin ticker. This is not necessarily bad. Darwinian selection is the ultimate governance mechanism. However, the immediate risk is liquidity fragmentation, exchange confusion, and a protracted period of uncertainty. The contrarian take is that we may end up with two viable Bitcoins, each optimized for a different use case. The real loser would be the illusion of a single, unitary store of value.
Takeaway
Forensics don't lie: Bitcoin is at its most fragile moment since 2017. The forced activation of BIP-110 represents a failure of governance that no technical workaround can fix. Investors holding Ordinals assets should consider them toxic until the dust settles. Bitcoin holders should prepare for a possible chain split and understand the replay attack risks. The question is not whether BIP-110 will pass — it's whether Bitcoin can survive its own guardians. Audit the promise, not the poster. The promise of immutability is tested not by code upgrades, but by the people who choose to enforce them.