BTC fork fight grows as BIP-110 stalls

TLDR

Bitcoins BIP-110 proposal is triggering a governance fight over a possible fork, even as miner support remains near zero and activation looks increasingly unlikely.

1. BIP-110 is a one-year Reduced Data soft fork that would limit non-financial data like Ordinals inscriptions on Bitcoin blocks, but current miner and node support are stuck in the low single digits.
2. Major figures such as Michael Saylor and Adam Back strongly oppose BIP-110, arguing it introduces censorship and dangerous precedent, while supporters frame it as a necessary fix for spam data.
3. With an August signaling window and almost no adoption, the most realistic risk is a small minority chain and short-term operational confusion, not a full-scale split of the main Bitcoin network.

Deep Dive

1. What BIP-110 Actually Does And Why It Is Stalling

BIP-110 (the Reduced Data Temporary Soft Fork) would add extra consensus rules for about one year, capping OP_RETURN and other payloads, and blocking most large arbitrary data chunks used for Ordinals, Runes, and similar activity. Coindesk notes that miner signaling is currently at zero, with past periods never exceeding about 1 percent.

Activation uses a user-activated soft-fork style mechanism with a lower threshold (55 percent of blocks in a period) than Bitcoins traditional 95 percent. With signaling and node adoption stuck in low single digits, stalling means the proposal is approaching its August deadline without the support needed for a main-chain rule change.

2. Why The Proposal Is So Controversial

Supporters, including developer Luke Dashjr and users of his Bitcoin Knots client, argue that inscriptions and other non-monetary data bloat the chain and undermine Bitcoins role as the worlds money by raising long-term storage costs for node operators. Crypto.news describes how they frame BIP-110 as a targeted fix for spam and data abuse that still preserves all known monetary use cases for new outputs.

Critics see something very different. Michael Saylor and Adam Back publicly rebuff BIP-110, warning that turning a spam dispute into a consensus rule change risks invalidating fee-paying transactions and sets a precedent for protocol-level content policing rather than free-market block space usage, as detailed by Cointelegraphs coverage. Back has said Bitcoin has robustly rejected BIP-110 and that pushing the rules without broad agreement is incompatible with Bitcoins permissionless ethos.

3. Fork Risk And What To Watch Next

Several analyses argue that, even with low signaling, there is still real coordination risk: if some miners, exchanges, and nodes enforce BIP-110 and others do not, blocks could diverge into a minority chain that follows the new rules and a dominant chain that ignores them. A detailed overview at news.bitcoin.com highlights an August 2026 window where mandatory signaling and potential activation cluster.

However, with no major mining pools backing BIP-110 and node adoption concentrated in alternative clients rather than Bitcoin Core, current evidence points toward the main Bitcoin chain rejecting the change. The main practical risks are temporary confusion around which chain some services follow, replay or settlement issues for niche forks, and volatility in any minority BIP-110 coin.

Confidence: moderate to high, because multiple independent reports agree on signaling levels, governance arguments, and timelines.

Conclusion

BIP-110 has turned a technical spam dispute into a wider fight over censorship, governance, and fork precedent, but stalled miner and node support mean it is unlikely to reshape Bitcoins main chain. For crypto users, the key is not guessing a new forks upside, but watching how miners, exchanges, and major custodians signal in August to gauge whether BIP-110 remains a niche minority experiment or becomes a more disruptive coordination event.