Bitcoin BIP-110 fork splits miner support

TLDR

Bitcoin has entered a contentious BIP-110 soft fork attempt, creating a minority chain backed by a tiny fraction of miners while most hash power stays on the main network.

1. BIP-110 is a one year anti spam rule set that restricts non financial data in Bitcoin blocks, now in a mandatory signaling phase with under 3 percent miner support.
2. At block 961,632, miners produced competing blocks, splitting Bitcoin into a dominant main chain and a slow BIP-110 fork that is lagging far behind.
3. The fork currently has little economic impact, but it raises replay and governance risks, so users should watch whether the minority chain dies out or changes proof of work.

Deep Dive

1. What BIP-110 Actually Does

BIP-110 is a Bitcoin Improvement Proposal that would temporarily tighten consensus rules to limit arbitrary non monetary data such as Ordinals style inscriptions and large OP_RETURN fields. It caps various script and data sizes and restricts some Taproot features for about one year, while leaving older outputs valid, as outlined in technical coverage.

Supporters argue this protects node operators from rising storage and bandwidth costs and refocuses Bitcoin on payments, while critics like Michael Saylor and Adam Back warn it could politicize block space and cause nodes to reject transactions that are currently valid. Miner signaling for the proposal has stayed around 2.5 to 2.6 percent, far below the 55 percent threshold BIP-110 uses for early activation.

2. How The Fork Split Miner Support

On August 8, 2026, at block height 961,632, Antpool mined a block that most of the network accepted, while BIP-110 aligned miner Roughnecks produced a competing block, creating two chains at the same height, as detailed in on chain fork reports from news.bitcoin.com. Standard nodes followed Antpools block, but BIP-110 enforcing nodes rejected it and followed Roughnecks instead.

Since then, the dominant chain has raced ahead by tens of blocks while the BIP-110 branch has added only one or two blocks and is falling further behind, with articles describing average block times of many hours on the fork and labeling it a likely failure given only about 2.6 percent signaling support. Some Ocean linked hash rate is even mining on the main chain, showing that pro BIP-110 miners are not unified.

3. Risks And What To Watch Next

During the current signaling window, BIP-110s stricter data rules are not yet active, and there is no built in replay protection between the branches. Analysts warn that this could expose users on the forked chain to replay and double spend style confusion if they treat both branches as equivalent, as noted in coverage of replay attack risks.

Developers around the fork have discussed a nuclear option of changing the proof of work algorithm on the minority chain to escape hostile miners, which would turn it into a more explicit altcoin style split rather than a soft fork. For most users who run standard Bitcoin Core or use major exchanges, the safest stance is to treat the main chain as canonical and avoid interacting with the minority chain unless they fully understand the risks and software they are using.

Conclusion

The BIP-110 episode shows Bitcoins governance working under stress, with a small group of node operators and miners trying to enforce stricter data limits despite almost no miner signaling. So far, the dominant chain is pulling away and the minority fork is struggling, suggesting limited direct impact on everyday BTC users but highlighting ongoing battles over how block space should be used and who gets to decide. Watching miner signaling, chain health, and any moves toward a proof of work change will clarify whether this remains a short lived fork or a lasting offshoot.