Hook
Over an 8-hour window on block height 961,632, the Bitcoin mainnet produced 49 blocks. The BIP-110 fork chain produced exactly 2. The first block arrived at 961,633, the second at 961,635. The mainnet pushed ahead to 961,681. That 48-block gap is not a statistical anomaly. It is a deterministic signal: the fork had no economic backing. No miner with real hashpower switched. The two blocks were likely mined by a hobbyist or a single node operator running a modified client. This is not a fork. It is a protest that failed to bootstrap a chain.
Context
BIP-110 is a Bitcoin Improvement Proposal aimed at restricting the use of transaction script data for non-financial purposes. Its primary target: Ordinals inscriptions, which embed arbitrary data (images, text, files) into Bitcoin transactions, consuming block space. The proposal set a 55% activation threshold within a 2,016-block difficulty period. Nodes supporting BIP-110 would reject blocks that did not signal readiness — a User-Activated Soft Fork (UASF) mechanism. In the preceding cycle, only 51 out of 2,016 blocks (2.53%) signaled support. Yet a subset of nodes activated the fork at height 961,632, refusing blocks without the signal. The result was a chain that crawled at 0.25 blocks per hour. The mainnet, meanwhile, continued at its regular pace of ~6 blocks per hour. This is not a one-off glitch; it is a structural failure of governance.
Core: Code-Level Autopsy
Let me be precise. The BIP-110 activation mechanism is a hybrid: it uses a miner-activated threshold (55% of blocks in a period) but enforces it via node-level rejection — a classic UASF. The threshold is set at 1,109 out of 2,016 blocks. In theory, this gives miners a clear target. In practice, the threshold is irrelevant when the actual support is 2.53%. The fork was triggered by nodes that decided to enforce the rule regardless of miner consent. The code does not lie: the chain is alive because a few nodes propagated blocks, but the lack of hashpower means those blocks have near-zero security. At 2 blocks in 8 hours, the chain is susceptible to a 51% attack by a single laptop. It cannot confirm transactions reliably. It cannot survive a network split.
From my experience auditing consensus-layer changes in 2022, I recall a similar dynamic during the SegWit UASF (BIP 148). That fork succeeded because miners eventually signaled to avoid a chain split. The difference? SegWit offered economic benefits: reduced transaction malleability, increased capacity, and a path to scaling. BIP-110 offers only restrictions. It reduces miner revenue by capping data-heavy transactions like Ordinals. Miners, being rational economic actors, saw no upside. The code is law, but the law is enforced by hashpower. The fork's failure is a perfect demonstration of the principle: "Code does not lie, only the documentation does." The documentation said the fork would change Bitcoin's data rules. The code executed a different reality.
Digging deeper: the fork's first block was mined by a node operator using a modified Bitcoin Core client. The second block followed hours later, likely from the same entity. There is no mining pool, no coordinated effort, no economic incentive. The chain's difficulty adjustment is still tied to the mainnet's schedule, meaning it will never produce blocks at a viable rate unless a massive amount of hashpower suddenly appears. That is not happening. The proposal's design assumed that a 55% threshold would create a "tipping point" — once enough nodes reject blocks, miners would switch to avoid losing revenue. But the threshold was never reached. The fork was premature. It is a case study in how UASF without miner support leads to a dead chain.
I have seen this pattern before. In 2022, while stress-testing Aave V2's liquidation logic under 150 crash scenarios, I learned that economic incentives are the ultimate governor of protocol behavior. Miners, like liquidators, respond to profit. If the fork does not align with their revenue stream, they ignore it. BIP-110's proponents expected miners to sacrifice Ordinals fee income for the sake of "pure money" ideology. The data shows miners chose the fees. The fork's 2-block chain is not a technical failure; it is an economic verdict.
Contrarian: The Blind Spot of Victory
The conventional narrative is that this fork's failure is a victory for Ordinals and a defeat for the "Bitcoin purity" camp. That is a surface-level read. The contrarian angle is that the fork's collapse reveals a deeper vulnerability: Bitcoin's governance is now a tug-of-war between node operators and miners, with no clear resolution. The 2-block chain is a signal that a minority is willing to break the rules to make a point. That minority may not have hashpower today, but they have code. They can fork again, with different parameters, at any time. The Ordinals ecosystem is celebrating a temporary reprieve, but the underlying conflict over block space usage is unresolved.
Moreover, the fork's failure does not mean that future restrictions are impossible. The miners' current stance is based on immediate fee income. If Ordinals transactions congest the network, raising fees for regular transfers, miners may eventually support a moderate limitation. The 2-block event is a warning shot: it shows that a determined group can force a chain split, even if short-lived. The next attempt might be more strategic — perhaps a BIP that limits only large inscriptions (>100 KB) while preserving small data. The support could be much higher. The blind spot is assuming that because the fork failed, the threat is gone. "If it cannot be verified, it cannot be trusted." The fork's failure does not verify the safety of Ordinals; it only verifies that miners currently prefer fees over ideology. That preference can change.
Another blind spot: the regulatory angle. The SEC has not commented on this fork, but the event demonstrates that Bitcoin's governance is messy. If a future fork succeeds in limiting data, it could de facto outlaw certain types of digital assets on Bitcoin. Regulators might see this as a form of self-regulation, or they might view it as market manipulation. The lack of a clear legal framework for such governance actions is a risk for institutional investors. The 2-block chain is a canary in the coal mine of consensus-layer politics.
Takeaway
The BIP-110 fork is a 2-block footnote in Bitcoin's history, but its implications are long-term. The event crystallizes the tension between two visions: Bitcoin as a settlement layer for financial transactions only, and Bitcoin as a data availability layer for any content. The fork failed because the economic incentive structure currently favors the latter. But that structure is not fixed. The next difficulty period could bring a different proposal. The next fork could have more blocks. "Security is a process, not a feature." Bitcoin's security against governance capture is not a one-time achievement; it is an ongoing negotiation between miners, nodes, and users. The 2-block chain is a reminder that this negotiation can break down, and when it does, the chain that survives is the one with the most economic weight. The rest is noise. Verify everything. Trust nothing.
