Eight hours. Two blocks. That was the entire production run of the BIP-110 fork chain — a would-be Bitcoin spin-off so under-resourced that it produced roughly one block every four hours while the main chain hummed through 49 blocks in the same window. At block height 961,632, a small collective of node operators activated what they framed as a user-activated soft fork, refusing to accept blocks that didn't advertise support for BIP-110. Their cause: restricting the volume of non-financial data being inscribed into Bitcoin's blockspace through Ordinals. Their result: a two-block memorial to an idea that the network's economic engine simply refused to fund.
I have spent years watching protocols rise and collapse, and I can tell you this was never about code. It was about who gets to decide what Bitcoin is for — and, more importantly, who pays when that question is answered incorrectly. From code audits to community heartbeats, every governance battle I have witnessed eventually collapses into the same brutal arithmetic: the side that controls the hash rate controls the outcome.
The Battle Over Blockspace
For most of Bitcoin's history, the question of what could be written onto the blockchain was settled by the network's limitations. Bitcoin's script language was deliberately constrained, and the block size limit made storing meaningful data on-chain expensive and impractical. The inscription craze, built on the Ordinals protocol, shattered that assumption. By enabling users to attach arbitrary data — images, text, even complete files — directly to individual satoshis, Ordinals turned Bitcoin into something its earliest architects never envisioned: a settlement network doubling as a data storage medium.
The numbers became too big to ignore. Inscription-heavy blocks began accounting for a substantial share of miner fee income. For a mining industry that had watched block subsidies shrink through successive halvings, this new revenue stream arrived like an unexpected lifeline. But for a vocal segment of node operators and maximalist thinkers, it was an abomination — a corruption of Bitcoin's monetary purity that had to be reversed at the protocol level.
BIP-110 became the formal expression of that grievance. Its proposal: a soft fork restricting transaction script data, effectively limiting the space available for inscription-style writes. The activation design borrowed from both the miner-activated soft fork (MASF) and user-activated soft fork (UASF) traditions, requiring 55% of blocks in a 2,016-block epoch — roughly two weeks — to signal support before the rules would lock in. The threshold was neither too high to be impossible, nor too low to be dismissible. In theory, it struck a balance. In practice, it never came close to mattering.
In the cycle preceding the fork, just 51 of 2,016 blocks — 2.53% — carried BIP-110's support signal. The proposal had no chance of meeting even a diminished threshold, and everyone involved knew it. Yet the fork was triggered anyway. Node operators rejected non-signaling blocks at height 961,632, effectively splitting from the main chain on their own terms.

What followed was eight hours of near-total chain inactivity. The fork chain produced two blocks, likely mined by the proposal's own supporters — alarm-clock miners who woke up, committed a token amount of hash power, and returned to the reality that the main chain was where the money lived. The two chains diverged by 48 blocks in eight hours. The BIP-110 chain was statistically indistinguishable from a dead network.
The Autopsy of a Stillborn Fork
The comparison with BIP-148, the 2017 UASF that successfully forced SegWit activation, is the most instructive diagnostic. When BIP-148's deadline approached, miners faced a genuine binary: support the user-activated soft fork or risk a catastrophic chain split at the moment of Bitcoin's greatest mainstream adoption. Roughly 95% of miners ultimately signaled support. The mechanism worked because the cost of non-cooperation was existential — every miner understood that a split would destroy the economic value embedded in their hardware.
BIP-110 offered no such existential threat. There was no deadline-driven panic, no shared catastrophe lurking in the failure to coordinate. There was only a restriction on revenue. With Ordinals fees flowing through their block templates, miners faced a straightforward calculation: why would they vote to cut off a revenue stream that required no additional work on their part? The proposal's 55% threshold was, in hindsight, a decorative number. When the economic incentive is one-directional, thresholds are theater.
There is a deeper governance lesson here, one I have carried since my 2017 forensic audit of the Telegram Open Network whitepaper, where a technically sophisticated project collapsed under misaligned stakeholder incentives. The BIP-110 process looked legitimate from a formal perspective: it had a number, a threshold, a signaling mechanism. But it lacked the fundamental ingredient of any successful protocol change — alignment of purpose with economics. A governance proposal is not simply a technical document. It is an economic proposition. And when the proposition reads "accept less revenue so the network can feel purer," you need more than clever mechanism design. You need power. In Bitcoin, power follows the hash rate.

The Contrarian Reading: Failure Was the Message
Now for the part that most market commentary will miss. The easy headline is "Ordinals wins, Bitcoin purists lose." That reading treats the fork's collapse as a permanent resolution of the data-usage question. Tempting. Comfortable. Almost certainly wrong.

Consider an alternative framework: the two-block chain was not a failed technical project; it was a successful political communication. The node operators behind this fork knew they could not win a miner vote. They triggered it anyway. Why? Because the act of forking — even a doomed one — forced the conversation onto their terms. For the cost of a few hours of hash waste, they injected the "blockspace purity" question back into public discourse, creating a news event where none would have existed had they simply filed another BIP into the repository. In communication terms, that is a bargain. We should expect more such actions, not fewer.
This matters for the market because the Ordinals ecosystem's window of safety is narrower than it appears. Miners rejected BIP-110 because the arithmetic was unfavorable. But arithmetic can shift. If inscription traffic continues growing — if mempool congestion pushes transaction fees for financial users toward unacceptable levels — the narrative flips. The same miners who ignored BIP-110 might then look favorably on a compromise proposal: restricting very large inscriptions while preserving small ones, or imposing fee-based disincentives on data-heavy transactions. Miners are not ideologically committed to Ordinals. They are committed to income. If the revenue curve inverts, the "silent veto" becomes a "silent endorsement."
More dangerous for the inscription ecosystem is the possibility that restriction efforts migrate from consensus-level changes to infrastructure-level filtering. Node software can quietly implement transaction relay policies that deprioritize large data-carrier transactions without touching consensus at all. That is the soft version of BIP-110 — harder to fight because it fragments across a decentralized network of independent node operators, and impossible to reject with a single miner vote. Trust is not a protocol, it is a practice — and node operators are free to practice their own definitions of acceptable chain usage.
The Real Story: The Miner's Veto Is the System
Stepping back, this episode crystallizes something structural about Bitcoin governance. The architecture has always separated the right to propose from the power to enforce. Anyone can write a BIP or trigger a node-level fork. But without hash power, those actions are letters to a dead address. BIP-110 is the latest proof of that theorem.
Building bridges where DeFi once built walls, I have observed that successful protocol upgrades are exercises in collective psychology as much as cryptography. The BIP-110 episode shows what happens when that collective psychology fractures. On one side: node operators with a deeply held conviction about Bitcoin's identity. On the other: an economic coalition of miners, holders, and an emerging inscription ecosystem. The gap between them is not technical. It is cultural. And cultural gaps do not heal through soft forks.
Liquidity flows, but culture remains. And right now, the culture of Bitcoin mining has quietly accepted the fee revenue from inscriptions — not out of passion for the technology, but from the simple arithmetic of survival. Every halving makes fee income more critical to the security budget. Miners will protect whatever feeds them. Today, that includes Ordinals.
The Takeaway: Watch the Compromise, Not the Confrontation
The practical lessons for investors and builders are straightforward. First, do not mistake the BIP-110 failure for a permanent guarantee. The Ordinals ecosystem is living on borrowed tolerance, not entrenched consensus. Second, monitor the three signals that matter more than any fork headline: new BIPs proposing graduated limits on inscription sizes; changes to default node software that deprioritize data-carrier transactions; and — most importantly — mining pool policies on accepting and ordering inscription-heavy transactions. Miners vote every ten minutes with their block templates. That is the ledger that matters.
Third, understand that Bitcoin has crossed a threshold. It is no longer a pure monetary network in the eyes of a large and active community; it is a shared ledger whose purpose is being actively negotiated. That negotiation will continue through forks, filters, and fee schedules. The most dangerous assumptions in this industry are the ones that mistake temporary equilibrium for permanent architecture.
The BIP-110 fork is already a footnote. Its two blocks will be orphaned by history within a year. But the governance fault lines it exposed — between node ideals and mining economics, between monetary purity and data functionality — will define Bitcoin's next decade. This week, Bitcoin's miners practiced their veto with a clarity no whitepaper could match. The question for the Ordinals community is whether they were watching closely enough to understand what the silence meant.