BIP-110 Has No Replay Protection. Ledger Just Told You the Trap.
On August 9, Ledger published a warning that should have been written into the protocol itself. BIP-110, a Bitcoin improvement proposal that could split the chain, is being discussed by some users as a chance to receive free fork coins. Ledger says the opposite: do not claim them. Do not move them. The reason is structural. The fork has no replay protection. A transaction signed on the BIP-110 chain can be rebroadcast on Bitcoin mainnet, and the Bitcoin that was sitting in your wallet is gone. This is not an exchange hack. It is not a phishing campaign. It is an absence of code-level separation. And in a market that treats airdrops as free money, that absence is the entire story. Code does not lie. Check the contract.
Ledger is a hardware wallet company. It is not a consensus layer. It does not determine which transactions are legal on Bitcoin. It signs whatever the user asks it to sign. That limitation matters. When a chain splits, both sides inherit the same transaction history and the same addresses. Every BTC holder on the snapshot receives an equal balance of the fork asset. That looks like a gift. But unless the fork changes the signature hash, the part of a transaction that commits to a specific network, every signature made on one chain is valid on the other. BIP-110, as described in Ledger's advisory, does not appear to change that binding. There is no replay protection. Ledger's message is therefore a confession as much as a warning: it can technically sign a transaction on the BIP-110 chain, but it cannot stop that same signature from being used against the user on mainnet. In practice, the user is being asked to accept a negative expected value trade. The fork coin might be worth something. The mainnet Bitcoin is worth something. A rational actor does not risk a certain asset for an uncertain one.
I have spent the last few years following capital flows through broken mechanisms. In 2022, I traced the collateral decay that preceded the Terra collapse. One lesson stayed with me: when an incentive is delivered through a mechanism that cannot verify user intent, the mechanism itself becomes the attack vector. BIP-110 is the same shape. The fork coin is free by design. The signature is reusable by design. The user is the only defense. That is not security. That is a dare.
Let's trace the attack path in plain sequence. A user holds Bitcoin in a self-custodial address at snapshot. The new chain activates and credits the equivalent fork coins. The user tries to sell those coins on the new chain. They create a transaction and sign it. The transaction's signature does not commit to a chain identifier. An attacker monitors the new chain's blocks, takes the exact raw transaction, and rebroadcasts it on Bitcoin mainnet. The bitcoin network sees a valid transaction because the signature is valid. The intended output of the fork-coin sale now receives Bitcoin. The user did not intend to spend mainnet BTC, but the code cannot tell the difference. There is no fraud in the cryptographic sense. The fraud is the missing chain binding.
Compare this with the 2017 Bitcoin Cash split. The parties on both sides added replay protection, using different signature hash flags or extra constraints, so that a transaction signed on one chain would be rejected on the other. That was not an elegant design choice. It became the industry baseline after the first large fork. BIP-110, based on Ledger's warning, does not meet that baseline. That is not a minor omission. It is a regression to a pre-2017 understanding of what a fork requires.
Some observers will ask why Ledger does not simply block the transaction at the device level. The answer is that wallet software cannot invent consensus rules. Ledger's firmware can reject a transaction with an obviously invalid signature or a low fee. It cannot reject a transaction that is valid under Bitcoin consensus but signed on the wrong chain, because the signature format is identical. The only way to protect users would be to add a chain ID or a distinguishing sighash flag. That change has to happen before the fork is created, inside the protocol. No wallet patch after the fact can do the job.
Let me make the math explicit. Assume a fork coin trades at 5 percent of Bitcoin's value after listing. If claiming it creates only a 1 percent probability of losing the mainnet Bitcoin, the expected value of the claim is still negative. The upside is 0.05 times the probability of success. The downside is 1.00 times the probability of replay. In a permissionless chain with an identical sighash, that probability is not controlled by the user's caution. It is controlled by the attacker's attention. An attacker needs to do nothing except wait for the first careless signature. That is not a low-probability tail risk. That is a structural invitation. Follow the smart money, not the tweets. Smart money is not rushing to claim a forked coin without replay protection. It is waiting for the fork to either add a distinct signature hash or show that it has no intention of doing so. Waiting costs a speculative upside. Acting can cost the principal.
The token economics of the fork coin make the problem worse. There is no team, no treasury, no unlock schedule, and no disclosed revenue source. The coin is created by duplicating Bitcoin's ledger, which means its entire supply appears at genesis. That is not a bad tokenomics model by accident. It is a tokenomics model with no obligation to the users who receive it. The coin has value only if someone is willing to buy it. If trusted exchanges are reluctant to list it because of replay risk, the bid side becomes thin and anonymous. A low-liquidity fork coin is exactly the environment where replay attacks become a spectator sport.
From an ecosystem perspective, BIP-110 is also a stress test for the rest of the stack. Custodians, exchange wallets, and DeFi bridges all assume transactions are chain-specific. If they are not, the failure moves beyond individual users. A single replayed transaction can drain a hot wallet that thought it was only handling fork coins. The only safe integration is to hard-code rejection of BIP-110 transactions until a chain identifier appears. That is a code change, not a policy statement.
The contrarian read is not that BIP-110 is a deliberate scam. It is that Ledger's warning is not neutral. Ledger is a French-regulated hardware wallet vendor. It benefits when users move toward the safest possible behavior and when it appears to be the responsible gatekeeper. Reinforcing the do-not-claim narrative reinforces its brand. That does not invalidate the technical warning. It just means the announcement should be read as product positioning as well as security research. The bigger blind spot is the user's assumption that free has no hidden cost. A fork coin with zero acquisition cost is not free if claiming it requires exposing a more valuable asset to an irreversible transaction. The market will eventually price this asymmetry. Exchanges are likely to delay listing any BIP-110 fork coin unless replay protection is added. Liquidity leaves before the crash hits. If the fork coin cannot be sold on a trusted venue, its implied value drops toward zero, and the only buyers left are the ones who know how to use the replay vector. That is not a market. That is a trap with a ticker.
This is why I keep coming back to on-chain data. A fork without replay protection is not a governance debate. It is a measurable technical condition. Look for the block where the first unprotected transaction appears. Look for the exchange cold wallet that moves BTC after the fork. The data will show the attack before the narrative catches up.
Some analysts will point to a fork coin's price and declare that the debate is over. That is correlation wearing a causal costume. Until the fork actually activates and transactions are replayed, no price graph can tell you whether the chain is safe. The code can. Check the sighash. If there is no chain identifier, there is no protection. If there is no protection, every fork-coin transaction is also a Bitcoin transaction with different packaging. The market may not price that distinction until the first batch of losses lands.
The next signal is not a tweet, not an exchange listing, and not another opinion piece. It is the new chain's implementation. If BIP-110 ships with a fork-specific sighash or some other replay protection, the risk drops to a familiar speculative level. I will still be skeptical of the fork coin's value, but at least the mechanics are no longer hostile. If it ships without one, the rational move is to treat every interaction with the fork as a potential mainnet loss. I am not claiming. The data does not support it. Code does not lie. The quiet part is that it does not need to.