TLDR
Ledger has warned Bitcoin (BTC) users that coins on the BIP-110 forked chain are risky because they lack replay protection and could endanger main chain BTC.
- BIP-110 created a stalled minority Bitcoin fork with very low miner support and only two blocks mined before activity essentially stopped.
- Ledger is warning that transactions involving BIP-110 fork coins can be replayed on the main Bitcoin chain, potentially moving your real BTC without your intent.
- BTC holders are safest treating BIP-110 fork coins as untrusted for now, avoiding spending or claiming them until exchanges and wallets implement clear protections.
Deep Dive
1. What BIP-110 Changed And Where The Fork Stands
BIP-110 is a proposed temporary soft fork that restricts how much non payment data can be stored in Bitcoin transactions, targeting things like Ordinals and other large payloads.
When mandatory signaling began around block 961,632, nodes enforcing BIP-110 split onto a minority chain, but miners did not follow. The enforcing branch mined only two blocks and then stalled while the main chain advanced dozens of blocks ahead. Reports show signaling peaked at about 2.5 percent of blocks, far below the 55 percent threshold, and the forked chain now produces blocks extremely slowly, making its coins illiquid and hard to use.
Economically, the BIP-110 fork looks like a failed side branch rather than a viable alternative Bitcoin network.
2. Ledgers Warning And Replay Attack Risk
Because BIP-110 does not include built in replay protection, transactions signed on the fork can still be valid on the main Bitcoin chain. Media coverage notes that Ledger warned users not to accept coins from the BIP-110 fork, highlighting that spending fork coins could also move corresponding BTC.
Explainers on the split show that pre fork UTXOs exist on both branches. If you send those fork coins to someone, the same transaction can often be rebroadcast on the main chain, letting the counterparty claim your real BTC from the identical inputs on Bitcoin. Analysts emphasize that users who leave pre split coins untouched do not create a transaction that can be replayed, which keeps their BTC safe despite the fork.
The danger is not losing coins automatically, but accidentally signing a transaction that is valid on both chains and lets someone drain the same inputs on mainnet.
3. Practical Steps For BTC Holders
For now, the safest posture is to ignore BIP-110 fork coins. That means not connecting your Ledger to nodes or services that treat the minority chain as Bitcoin, and not trying to claim or sell fork balances. Coverage of the split and replay risk, including detailed warnings from developers on replay attacks across both chains, supports this cautious stance.
If you simply hold BTC on the main chain and do not sign transactions involving BIP-110 fork outputs, you are not exposed to replay. If exchanges eventually list fork coins, look for clear guidance on how they separate balances and whether they implement replay protections such as different address formats, opt in claims, or protective sweep procedures.
Treat fork coins as experimental and potentially hazardous until major wallets and exchanges publish explicit, technical steps that keep your main chain BTC insulated.
Conclusion
Ledgers warning reflects a real technical issue rather than price speculation. BIP-110 has produced a weak, stalled fork without replay protection, so any attempt to monetize its coins can create pathways for attackers or counterparties to pull real BTC from identical transaction inputs on the main chain. Until infrastructure clearly separates the two histories, Bitcoin holders are better served by leaving pre fork balances untouched and focusing on the dominant Bitcoin chain.
CoinsKid.Com