Bitcoin’s long-running dispute over transaction data limits moved from debate to a live network split when supporters of BIP-110 began following a separate chain at block 961,632. The BIP-110 minority chain accepted a stricter policy for data carried in transactions, while the overwhelmingly larger network continued under the existing rules. What followed was less a competitive fork than a practical demonstration of how difficult it is to sustain a blockchain without meaningful miner support.
The new branch produced two blocks after the split and then stopped advancing. By the evening after the fork, it was already several blocks behind the main Bitcoin network. That gap matters because a blockchain’s usefulness depends on predictable confirmations, active mining, accessible infrastructure, and confidence that transactions will settle. A chain that advances only intermittently cannot provide those conditions, even if its supporters strongly prefer its policy choices.
What BIP-110 Tried to Change
BIP-110 proposed a one-year restriction on the amount of arbitrary data that nodes would relay or accept through OP_RETURN outputs and certain witness constructions. Supporters framed the change as a way to keep Bitcoin focused on monetary transactions and reduce demand for block space from inscriptions and other data-heavy uses. Opponents argued that the policy would add complexity, encourage workarounds, and divide the network without preventing determined users from publishing data.
The distinction between relay policy and consensus rules is important. Node operators can choose which unconfirmed transactions they relay, but miners ultimately decide which valid transactions enter blocks. A local policy can affect how transactions spread through the peer-to-peer network without changing what the broader network considers a valid block. BIP-110 went further by coordinating nodes around a rule set that no longer followed the same chain once a disallowed transaction appeared.
The Trigger at Block 961,632
The split occurred when the main chain included activity the BIP-110 implementation would not accept. From that point, participating nodes treated a different block history as authoritative. The majority chain continued producing blocks at Bitcoin’s normal cadence because nearly all active hashpower remained there. The minority branch inherited the same mining difficulty but had only a small fraction of the computing power needed to meet it.
That inherited difficulty created the immediate bottleneck. Bitcoin adjusts mining difficulty every 2,016 blocks, based on how quickly the preceding interval was mined. A new minority chain does not receive an instant reduction simply because most miners decline to follow it. With very limited hashpower, reaching the next adjustment could take many months rather than roughly two weeks. Until then, every block is a low-probability event.
Why Hashpower Matters More Than Node Signaling
Public signaling around BIP-110 had shown a visible base of compatible nodes, but node counts do not translate directly into block production. A non-mining node verifies and relays data; it does not contribute the proof-of-work that extends the chain. A network can therefore show substantial software adoption while still lacking the miners required to make that software’s preferred history usable.
Estimates before the fork placed mining support far below the share of nodes signaling for BIP-110. The post-split slowdown confirmed that mismatch. This is a recurring lesson in proof-of-work governance: developers, node operators, miners, businesses, and users influence the system in different ways, and a durable rule change usually requires coordination across several groups.
The stalled branch also creates practical security questions. If both chains share transaction formats and keys, a transaction intended for one network may be valid on the other unless replay protection or careful coin handling separates them. Wallet providers and exchanges must decide whether to recognize the minority asset, how many confirmations to require, and whether deposits or withdrawals can be supported safely. Sparse blocks make each of those decisions harder.
Economic Finality Versus Formal Validity
A block can satisfy a chain’s formal rules without attracting economic use. For users, finality is partly social and economic: they need liquidity, counterparties, infrastructure, and confidence that reorganizations are unlikely. The main Bitcoin chain retained those advantages because its miners, markets, and services continued operating without interruption.
The BIP-110 minority chain may technically resume if miners direct more hashpower toward it. Yet intermittent mining alone would not solve the broader coordination problem. It would need enough sustained work to reach a difficulty adjustment, plus wallets, explorers, exchanges, and users willing to treat the branch as a distinct network. None of those outcomes follows automatically from running compatible node software.
What Comes Next for the BIP-110 Minority Chain
The immediate question is whether supporters can recruit persistent hashpower or engineer a safe path through the long difficulty interval. Any attempt to change difficulty rules after the split would itself be another consensus decision and could further fragment participants. Leaving the rules untouched preserves the proposal’s original design but may keep block production impractically slow.
For the main network, the dispute over transaction data is not finished. Operators can still use local relay policies, miners can still select transactions according to their own criteria, and developers can continue proposing changes. The fork does, however, set a real-world cost for escalating a policy disagreement into incompatible consensus behavior.
The BIP-110 minority chain is therefore most useful as a governance case study. It shows that visible node support can express dissatisfaction, but it cannot substitute for mining security or market coordination. Unless those pieces converge, the BIP-110 minority chain will remain a stalled branch rather than a functioning alternative to Bitcoin.
