A replay attack is a cryptographic failure. Yet, a proposed Bitcoin fork threatens to repeat this failure. On August 9, Ledger—the hardware wallet giant—issued a stark warning: users should not claim any potential fork coin from a chain called “BIP-110” because the transaction signatures are identical to Bitcoin’s. The warning is not mere caution; it is a confirmation of a broken design. The fork, if it exists, lacks replay protection. And the name “BIP-110” is historically inaccurate—a tell that the proponents are either ignorant or intentionally misleading.
Context: The Ghost of BIP-110
BIP-110, in Bitcoin’s history, is the number assigned to CHECKSEQUENCEVERIFY (CSV)—a soft fork activated in 2016 that introduced relative locktime. It was part of a bundle (BIP-68, BIP-112, BIP-113) that prepped Bitcoin for SegWit. So when a group claims to be forking Bitcoin under the banner “BIP-110,” they are either referencing a proposal that already exists—and thus cannot be a new fork—or they are using the number as a political signal to roll back changes. The more plausible scenario: a faction threatens to run a node version that excludes CSV and later soft forks, creating a chain that is technically compatible with Bitcoin’s legacy transaction format. No replay protection is built into this design.
Ledger’s statement that their devices “can technically sign such transactions” confirms that the fork’s transaction format is identical to Bitcoin’s. This is the green light for a replay attack. The user who signs a transaction on the fork chain—whether to claim the “free” coin or to move it—accidentally broadcasts the same signature on Bitcoin’s mainnet, losing their BTC.
Core: The Mechanics of a Self-Destructive Fork
Replay attacks are not theoretical. They are a direct consequence of shared history and identical signature schemes. When two chains share the same genesis block and the same address format, a transaction signed for one chain is valid on the other. The only defense is a chain identifier—a marker that distinguishes transactions. Bitcoin Cash used SIGHASH_FORKID; Ethereum Classic suffered years of replay attacks because no such mechanism was added.
This fork, if it appears, will have zero protection. That means no exchange will list it. No exchange will risk the legal and operational liability of handling a token that can trigger a loss of mainnet BTC. Without exchange liquidity, the fork coin becomes a dead token—impossible to sell, impossible to value. The economic calculation is brutal:
- Claim cost: You need to split your BTC into a new wallet, sign a transaction on the fork chain, and risk accidentally broadcasting that signature on Bitcoin. Even with careful isolation, a single mistake—and your BTC is gone.
- Potential reward: A token with no trading pair, no community, and no use case. The historical precedent of Bitcoin forks (BCH, BSV, BTG) shows a rapid decay to near-zero value. BCH, the most successful, now trades at less than 1% of Bitcoin’s market cap.
Based on my years auditing blockchain protocols, I have seen replay attacks destroy portfolios. In 2019, while analyzing a cross-chain bridge, I discovered that a “simple” fork without replay protection could drain user funds. The math is simple: the risk of losing your mainnet BTC far exceeds any speculative gain from a fork coin.
I compiled a risk-assessment checklist for this event:
- [x] No replay protection mechanism (FAIL)
- [x] No public code repository (FAIL)
- [x] No testnet or miner support announced (FAIL)
- [x] No exchange listing commitment (FAIL)
- [ ] Known development team (?)
- [ ] Clear rationale for fork (?)
The only passing mark is the lack of a known team. That is not a strength.
Contrarian: The Blind Spot of “Safe Claiming”
Some users believe they can claim the fork coin safely using a dedicated wallet or by waiting for a split tool. This is a dangerous illusion. Without replay protection, any transaction on the fork chain is a replay vector. Even if you use a separate wallet, the moment you sign a transaction on the fork chain—even to test the balance—you are broadcasting a valid Bitcoin transaction. The only way to safely claim is to split the chain’s UTXO set using a “coin split” service, but that requires the fork to have a distinguishable feature. This fork has none.
The fork proponents claim they are creating a “purer” Bitcoin. But the technical reality is that they are creating a security nightmare. The irony: they oppose soft forks like CSV and Taproot, yet they are willing to sacrifice the very security that makes Bitcoin valuable. The blind spot is that the fork’s existence is its own destruction—the more people try to claim, the more they lose.
Takeaway: The Lesson Not Learned
This fork will likely fizzle out. The market has moved on from Bitcoin forks; the narrative is dead. But the lessons from 2017 remain unlearned. Security is not a feature; it is a prerequisite. Complexity hides risk; simplicity reveals it. Until the next fork, the question is: will you be the one replaying the transaction, or the one losing the coins?
Proofs verify truth, but context verifies intent. In this case, both are missing.