The fork that wasn't supposed to happen just proved why no one wanted it in the first place.
The Summary
- BIP-110 activated with less than 3% miner support, created a minority chain that mined two blocks then stalled due to insufficient hashpower
- Both chains still accept identical transactions, creating a replay attack risk where selling fork coins could accidentally sell real BTC
- Bitcoin holders face a dangerous choice: do nothing or risk losing actual bitcoin by trying to dump worthless fork tokens
The Signal
When BIP-110 hit its activation threshold at block 961,632, it became the most unwanted fork in Bitcoin history. Less than 3% of miners supported it. Influential Bitcoin developers and commentators lined up against it. And yet it activated anyway, splitting the network into two chains: the main Bitcoin blockchain that everyone actually uses, and a ghost chain limping along with a microscopic fraction of the hashpower.
The technical problem is elegant in its brutality. The breakaway chain inherited Bitcoin's full mining difficulty but only commands a sliver of the network's computational power. Bitcoin difficulty adjusts every 2,016 blocks to keep block times around 10 minutes. BIP-110's chain started with that same difficulty calibrated for Bitcoin's entire mining network, but it only has maybe 2-3% of the hashpower. Do the math: blocks that should take 10 minutes now take hours.
"The breakaway chain inherited bitcoin's mining difficulty with only a tiny share of hashpower, leaving blocks hours apart."
The fork managed to mine exactly two blocks before grinding to a near halt. This isn't a technical bug. It's the network speaking. When you fork Bitcoin without miner support, you get a blockchain that can barely produce blocks. And without blocks, you don't have a functioning network. You have digital stillbirth.
But here's where it gets dangerous for regular holders. Both chains currently accept the same transaction signatures. If you try to sell your BIP-110 fork coins on an exchange, someone could take that signed transaction and replay it on the real Bitcoin network. You think you're dumping worthless fork tokens. Actually, you just sold your real BTC.
Key risks for holders:
- Selling fork coins can result in selling actual Bitcoin via replay attacks
- No clear chain separation mechanism exists yet
- Exchanges may list fork tokens before replay protection is implemented
- Doing nothing is currently the only safe move
Bitcoin developer warnings emphasize that attempting to transact on the fork chain before proper replay protection exists puts real holdings at risk. The safest move is inaction. Wait for the chains to separate properly, or for the fork chain to die completely.
This isn't the first contentious Bitcoin fork. Bitcoin Cash in 2017 had actual miner support and a functioning network from day one. It still became a sideshow. BIP-110 doesn't even have that. It has two blocks and a prayer.
The Implication
Watch how this resolves. If the BIP-110 chain dies within days, it sets a clear precedent: you can't fork Bitcoin without miner consensus, no matter how clever your activation mechanism. If it somehow survives and gains hashpower, that's a different signal entirely. It would mean Bitcoin's governance is more fragile than the maximalists claim.
For holders: touch nothing. Don't try to claim fork coins, don't send transactions, don't interact with any service claiming to support BIP-110 until replay protection is confirmed. The upside is zero. The downside is losing actual Bitcoin to a technical quirk of a dying fork.
For the broader crypto ecosystem: this is what credible neutrality looks like when stress tested. Bitcoin didn't stop the fork. The market did. No one showed up. That's more powerful than any governance vote.