Miner support for BIP-110 has been stuck below 1% for weeks. Yet the proposal’s mandatory activation window opens in eight days. That is not a typo. A protocol change that less than one percent of the network’s security providers endorse is about to be forced through by a handful of node operators. The last time Bitcoin faced such a low-consensus hard fork, it created Bitcoin Cash. This time the stakes are higher because the target is not block size but the very definition of what Bitcoin is allowed to store.
To understand the hostility, you must trace the conflict back to early 2023. The Ordinals protocol introduced the ability to inscribe arbitrary data—images, text, even entire PDFs—onto individual satoshis. Then came BRC-20 tokens, then Runes. Bitcoin, designed as a peer-to-peer electronic cash system, suddenly became a settlement layer for digital artifacts and meme tokens. Transaction fees spiked and the UTXO set swelled. For the purists, this was an existential violation. In their view, Bitcoin’s block space exists for value transfer, not for data hoarding. BIP-110, authored by Dathon Ohm with contributions from Luke Dashjr, is their weapon. It caps non-transaction data per output at 256 bytes, effectively outlawing large inscriptions.
The core of the proposal is deceptively simple. It modifies the OP_RETURN rule and further restricts any output that does not represent a genuine value transfer. Nodes running the new rules will reject any UTXO that contains more than 256 bytes of non-canonical data. This is a consensus-layer filter designed to extinguish application-layer activity. The activation mechanism, however, is where the danger lies. BIP-110 uses a mandatory activation window set to begin on August 7, 2025. Once that window opens, any node that upgrades will treat unmarked blocks as invalid—regardless of how much hash power those blocks carry. The proposal essentially bypasses miner consent. The code does not ask for permission; it enforces intent.
My forensic work on prior network splits taught me to watch the data trails closely. On-chain signals confirm that miners are voting with their hash. The bip110.org dashboard shows that only 0.3% of blocks in the last 144 have been flagged with support. The remaining 99.7% are silent opposition. Yet the mandatory activation is not contingent on miner sentiment. If even a small cluster of economically significant nodes—exchanges, large custodians, wallet providers—upgrades to the new rules, the network faces a partition. Transactions valid on the majority chain will be invalid on the BIP-110 chain. UTXOs that contain inscription data will become unspendable on the forked side. The block chain remembers what humans forget, but a fork splits that memory.
Complexity is often a disguise for theft. The Ordinals community has already proposed a workaround: split large inscriptions into 256-byte chunks, each carried by a compliant UTXO. Technically this bypasses the 256-byte rule, but the cost is severe. A single 100 KB image would require nearly 400 separate transactions, each paying its own fee. The aggregate block space consumed would be higher than the original single-inscription approach. Worse, the workaround relies on a specific interpretation of BIP-110’s wording that the proposal’s authors dispute. Luke Dashjr himself has stated that the split-chunk trick violates the spirit of the rule and will be addressed in a future revision. What the market sees as a Hail Mary pass is actually a temporary patch on a moving target.
Let me step back and apply the same analytical lens I used during the Terra/Luna investigation. In 2022, I cross-referenced Anchor Protocol’s whitepaper with on-chain transaction logs and demonstrated that the 19% APY was mathematically impossible without perpetual new money inflow. The same discipline applies here. When I audit a protocol, I isolate each variable’s dependency. For BIP-110, the critical variables are miner revenue composition and UTXO growth. Before Ordinals, transaction fees represented roughly 5-10% of miner income. After Runes launched in April 2024, fee percentages spiked to over 30% during peak activity. BIP-110, if enforced, would crush that revenue stream. Miners are rational economic actors. Their near-zero support for the proposal is not ideological; it is self-preservation. The market is pricing in a political battle, but the underlying driver is economic.
Ponzi schemes leave trails in the data. The fee boom from inscriptions is not a Ponzi, but it is fragile. It depends on speculative demand for digital artifacts that may vanish overnight if BIP-110 succeeds. The ORDI token, for example, has a market cap that is entirely contingent on the current inscription mechanism being legal. If BIP-110 renders that mechanism unenforceable on the dominant chain, ORDI becomes a collector’s item with no finality. The same applies to every BRC-20 token. Auditing the edges, not just the center, reveals that the entire asset class is a derivative of a single consensus-layer assumption. Change the assumption, and the derivative collapses.
Now the contrarian angle. The pro-BIP-110 camp has a legitimate concern. Node operators run full archive nodes out of goodwill. Storing terabytes of inscription data forever imposes a cost on volunteers with no corresponding reward. The argument that “Bitcoin is not the right place for NFT storage” has technical merit. Lightning Network, for instance, was designed for high-volume payments precisely to avoid bloating the UTXO set. But the solution BIP-110 proposes is the wrong surgical instrument. Capping data to 256 bytes does not eliminate spam; it merely changes its form. The chunked-inscription workaround would increase the number of transactions per inscription by orders of magnitude, potentially worsening UTXO bloat. And the mandatory activation window sets a precedent that governance by fiat is acceptable as long as the code compels it. That precedent is more dangerous than a few JPEGs.
What the bulls got right is the existential question: should Bitcoin remain a purpose-built value layer, or should it evolve into a general-purpose data base? The former keeps the network lean and attack-resistant. The latter opens the door to economic density but also to state bloat and greater centralization pressure on node operators. The error is in believing the change can be enforced through software rather than consensus. A hard fork does not resolve the disagreement; it institutionalizes it. Both chains become weaker. Code does not lie; intent does. The intent of BIP-110’s authors is to reclaim a pure vision, but the execution guarantees a fractured reality.
Verify the hash, trust no one. The next eight days will determine whether Bitcoin splits into two mutually hostile networks. A fork would not resolve the underlying demand for data storage. Users who want to inscribe will migrate to the chain that allows it. Miners who want fees will follow the users. The BIP-110 chain may end up as a ghost chain with minimal hash and zero economic activity, except that it will be maintained by a small group of ideologically committed node operators. That scenario is not victory; it is isolation. The alternative—where BIP-110 fails to activate because too few nodes implement it—leaves Bitcoin unchanged but exposes the fragility of its governance model.
From my experience auditing the 0x Protocol v2 in 2017, I learned that a single overlooked integer overflow can cascade into system-wide failure. The same principle applies here. The overlooked variable in BIP-110 is human coordination. The proposal assumes that nodes will upgrade because the code says so. It ignores that network participants are sovereign actors. Miners will not switch to a chain that destroys their primary revenue driver. Exchanges will not list a fork that orphans their customers’ UTXOs. The silence is the only honest ledger: the 99.7% of unmarked blocks are the network’s real vote.
Silence is the only honest ledger. Bitcoin is about to face its most consequential stress test since the 2017 block size wars. But this time the battlefield is not block size; it is what constitutes a valid transfer. The outcome will define whether Bitcoin remains a system of absolute rules or becomes a system that can be patched by a determined minority. The answer is written in the source code, but the execution will be decided by hash power and economic gravity. Auditors like me will trace the transaction flows. Histories like the Terra collapse teach that when the model breaks, the first to run survive. Prepare for volatility. Watch the activation window. And remember that code does not lie—but the humans who write it do.