Tracing the code back to its genesis block, I see a pattern: every Bitcoin fork that was born from ideological purity, not economic incentive, has bled out within a month. The BIP-110 chain, now 18 blocks behind the mainnet, is no exception.
On August 9, 2026, at block height 961,632, a set of Bitcoin nodes running a custom patch decided they had seen enough. The target was Ordinals—the data embedding protocol that had turned Bitcoin's block space into a digital graffiti wall. For months, BRC-20 tokens and NFT inscriptions had clogged the mempool, pushing transaction fees higher for ordinary users. The core developers behind BIP-110 proposed a solution: a soft fork that would reject any block containing non-financial data, effectively outlawing Ordinals. But the fork was not a clean split. It was a UASF (User-Activated Soft Fork) pushed by a minority of node operators, not miners. The result was a schism that produced a chain so weak it could barely crawl.
Context: The Ordinals War and the Birth of BIP-110
To understand why this fork matters, you must rewind to 2023, when Casey Rodarmor released the Ordinals protocol. By embedding data—images, text, even entire application files—into Bitcoin's witness data, Ordinals turned the scarce blockspace into a commodity. The flood of inscriptions pushed the average transaction fee from $2 to over $20 during peak periods. For Bitcoin purists, this was a violation of the network's original intent: to serve as a peer-to-peer electronic cash system, not a decentralized storage platform.
BIP-110 was proposed as a containment mechanism. Its technical specification was simple: any block that included a transaction with an OP_RETURN output exceeding 80 bytes of non-financial data would be considered invalid. The fork would be activated via miner signaling, requiring 95% of blocks in a 2,016-block difficulty period to include a support flag. If the threshold was not met, the fork would expire after approximately one year—a timed sunset clause.
But here is the forensic detail the whitepapers gloss over: the signaling threshold was never even close to being reached. In the last signaling period, only 51 blocks—a mere 2.53% of the total—carried the BIP-110 flag. The fork was dead on arrival in terms of miner support. Yet, a small group of node operators, running a UASF patch, forced the issue. They refused to accept blocks that did not contain the signal. At block 961,632, they split.
Core: The 18-Block Gap and the Arithmetic of Failure
Let me walk you through the numbers. The mainnet reached block 961,651 within hours of the fork. The BIP-110 chain? It stalled at block 961,633. That is a gap of 18 blocks. In a system where blocks are supposed to be produced every 10 minutes, the BIP-110 chain produced only 1 block in the time the mainnet produced 19. Follow the smart contract, ignore the whitepaper. The math is brutal: the fork chain has approximately 5% of the mainnet's hash rate. With that level of security, it is vulnerable to a 51% attack by any miner with a few ASICs and a grudge.
Where liquidity flows, truth eventually pools. And the truth here is that the BIP-110 chain has no liquidity, no hash, and no future.
Decoding the signal hidden in the noise, I can see the insider dynamics. The 51 blocks that signaled support were not random. Over 80% of them came from three mining pools: F2Pool, Poolin, and a small Chinese pool called BTC.TOP. These are pools that have historically been sympathetic to Bitcoin's original vision—they are not the mercenary hashers that dominate the network. The rest of the mining community, including AntPool and ViaBTC, remained silent. This is not a rebellion; it is a protest vote.
Composability is a double-edged sword. In this case, the composability of Bitcoin's consensus rules allowed a fork to be created, but the same composability makes it impossible for the fork to survive without economic gravity.
Contrarian: The Hidden Cost of 'Cleaning' the Chain
Now, let me challenge the narrative. The standard view is that the BIP-110 fork is a failed attempt to restore Bitcoin's purity. But I see a different story: the fork is a pressure valve. The fact that it exists, even as a weak chain, signals that a significant portion of the node operator community is willing to risk a split to enforce a data policy. This is not just about Ordinals. It is about the growing tension between Bitcoin's 'immutable ledger' ethos and its 'attractive platform' reality.
Bubbles burst, but architecture remains. The BIP-110 chain, though weak, has created a template. If Ordinals continue to bloat the mempool, and if transaction fees remain high, the next fork may not be a UASF minority—it could be a miner-led majority. The 2.53% support today could become 40% in six months, if the fee pressure becomes unbearable.
Moreover, the fork's existence exposes a blind spot in the Ordinals ecosystem. BRC-20 tokens, which rely on the ability to inscribe data, are now vulnerable to a change in the consensus rules. The holders of these tokens cannot assume that the data layer will remain accessible. This is a systemic risk that the market has not priced in.
Takeaway
The BIP-110 fork is not a dying chain; it is a canary in the coal mine. It tells us that the 'war on Ordinals' is not over. It will escalate. The next battle will be fought not in the code, but in the mempool, where transaction fees are the ultimate arbiter. Watch the fee rates, not the block height. When the average fee exceeds $30 for a week straight, the miners will start to listen. The BIP-110 chain will die, but its ghost will haunt the next debate.