TLDR
The BIP-110 Bitcoin (BTC) soft-fork attempt has effectively stalled, leaving a tiny minority chain frozen while the main Bitcoin network continues as normal.
- A BIP-110-enforcing branch split off at block 961,632, produced only two blocks, then stalled as miner support stayed below about 3%.
- BIP-110 aimed to temporarily restrict non-financial data like Ordinals inscriptions, but drew strong criticism for changing consensus rules with weak support.
- For most BTC users, the impact is minimal so far, but the episode highlights replay risks and how hard it is to change Bitcoin without broad economic consensus.
Deep Dive
1. Fork Launch And Stall
When BIP-110 entered its mandatory signaling phase around block 961,632, a minority of nodes began enforcing its rules and rejecting non-signaling blocks. That created a breakaway chain which mined just two blocks (961,632 and 961,633) before effectively stopping, while the main chain advanced by dozens of blocks ahead. Reports show the enforcing branch lagging by 80110 blocks and producing blocks hours apart instead of every 10 minutes, confirming that it has stalled with negligible hashpower behind it. One detailed analysis notes that only about 2.5% of recent blocks signaled for BIP-110, far below the 55% threshold its own rules require.
The situation worsened when Roughnecks, the group that mined the only two BIP-110 blocks, publicly stopped BIP-110 mining, and Ocean pools hash rate collapsed by over 90 percent. With the minority chain inheriting full Bitcoin difficulty and almost no miners, there is no realistic path for it to catch up. From a practical standpoint, this makes the BIP-110 fork attempt a failed experiment rather than a competing version of Bitcoin.
2. What BIP-110 Tried To Change
BIP-110, branded the Reduced Data Temporary Softfork, proposed a roughly one-year soft fork that would cap various ways of putting arbitrary data into Bitcoin transactions. It would re-tighten limits on OP_RETURN payloads and certain Taproot-based constructions, directly impacting protocols like Ordinals and similar data-heavy uses of Bitcoin block space. A clear overview notes that it would temporarily invalidate some currently valid, fee-paying transactions to enforce these limits, which critics saw as crossing a line on Bitcoins neutrality and predictability. A major explainer describes the core tension: supporters want to protect Bitcoins role as money, while opponents argue this is consensus-level censorship.
The proposal used a user-activated soft fork (UASF) style approach: node operators could enforce the new rules even without strong miner backing, aiming for a 55% signaling threshold instead of Bitcoins traditional 95%. That design, plus the risk of freezing some scripts and UTXOs, drew strong opposition from figures like Adam Back and Michael Saylor, who warned that BIP-110 could turn a spam argument into a dangerous consensus precedent.
3. Implications And What To Watch
For everyday BTC holders who do nothing, the main chain continues unaffected, and their coins sit on the dominant network. The stalled BIP-110 chain is economically irrelevant so far, but its mere existence creates a theoretical replay risk for anyone trying to transact on both branches, because pre-split coins share the same history and some transactions could be valid on both chains. In practice, that only matters if exchanges or users start trading the minority fork, which has not meaningfully happened yet.
The bigger takeaway is governance: the episode shows that a small group of motivated node operators cannot unilaterally redefine Bitcoin if miners, exchanges and most economic actors do not follow. It also underlines that proposals which invalidate previously valid transactions face a very high bar for consensus. Going forward, the key things to watch are whether BIP-110 is formally abandoned, whether its backers try a new proof-of-work or separate chain, and how the broader community chooses to address spam and Ordinals-style usage via policy rather than contentious soft forks.
Bitcoins main chain remains the de facto BTC, and attempts to force through controversial protocol changes with thin support are likely to stall; users should be cautious about interacting with minority forks until their status is clear.
Conclusion
The stalled BIP-110 fork shows that Bitcoins consensus still heavily depends on broad miner and economic support, not just vocal node signaling. While the attempt to restrict non-financial data sparked a serious debate, the markets response has been to ignore the minority chain and keep building on the main one. For BTC holders and builders, the episode is a governance stress test: it reinforces both the difficulty of changing Bitcoins rules and the importance of careful, widely supported evolution over unilateral experiments.
CoinsKid.Com