Fork detected. Volatility imminent. On August 9, Ledger posted a security notice that should have been impossible: a Bitcoin fork labeled “BIP-110” is threatening to split the network, and the hardware wallet giant is telling users to wait for replay protection before moving a single satoshi. The warning is technically sound, brutally necessary, and almost certainly built around a phantom. BIP-110 is not a new proposal. It is CHECKSEQUENCEVERIFY, the relative time lock soft fork that activated on Bitcoin in 2016. You cannot create a new chain by “proposing” a BIP that Bitcoin already locked into its consensus history years ago. Yet Ledger, the most trusted custodian device in the industry, says its firmware can sign transactions on the fork. That suggests code exists, nodes may be running, and someone is gearing up for a chain split — under a BIP number that history already spent.
The real story is not replay protection. The real story is a rollback fork pretending to be an upgrade. Read that sentence again before you touch your cold wallet.
Context: The Fork That Can’t Be Named
Ledger’s notice doesn’t need to name the belligerents. The infrastructure layer is the alarm system. Ledger’s job is to protect the user when the social contract fails. It has confirmed two hard facts: first, its devices are technically capable of signing transactions on the fork; second, the fork has not implemented replay protection. Those two facts together are enough to cause serious damage. This is not a tempest in a testnet. This is a cold wallet provider, with decades of collective engineering experience, choosing to issue a public warning. The last time a major hardware wallet did something that loud, the market actually listened.
Replay attack mechanics are brutal. Before a fork, chain A and chain B share the same transaction history. Bitcoin ownership on both chains is proven with the same addresses, the same private keys, and the same signature algorithm. If both chains accept identical transaction formats, a signature generated on one chain is valid on the other. An attacker simply takes a signed transaction that a user broadcasts on the fork chain and rebroadcasts that exact raw transaction on Bitcoin mainnet. The user thought they were spending fork tokens. In reality, they just authorized a second spend of the same UTXO on the original chain. The funds move exactly as signed. And now the attacker controls the victim’s mainnet BTC.
This is not a theoretical edge case. It is the same vulnerability that haunted Ethereum Classic for years after the 2016 DAO fork. It is the reason Bitcoin Cash added SIGHASH_FORKID. Without that chain-specific sighash flag, BCH would have burned users alive. The BIP-110 fork — or whatever it actually is — has apparently added no such protection. That is not a technical oversight. It is a design choice. And given that Ledger has already confirmed the fork is technically operable, the absence of replay protection is either gross negligence or intentional malice.
Based on my audit experience with EigenLayer’s slasher contracts in 2023, I learned to treat “it works” and “it is safe” as two completely different statements. The EigenLayer code worked. But a withdrawal queue edge case made it unsafe. Here, the logic review is simpler. Two chains. One transaction format. Zero replay protection. The conclusion writes itself. A transaction signed on the fork is a transaction signed on Bitcoin. There is no gray area.
Core: What Ledger’s Warning Actually Reveals
Let’s dig into the engineering signals, because the alert contains more information than Ledger intended.
First, Ledger did not say “we are investigating compatibility.” It said the device can technically sign these transactions. That statement could not have been made without firmware-level testing. Meaning: the fork’s transaction format is close enough to Bitcoin’s to pass Ledger’s own parsing, rendering, and signing pipeline. That is a meaningful data point. The fork is not a hypothetical. It has, at minimum, a working transaction engine that maps almost one-to-one onto Bitcoin’s.
Second, Ledger’s advice to wait for replay protection reveals the underlying asymmetry. The fork’s developers have not delivered a protection mechanism, but they still want users to move coins. That combination — an operable chain, no replay protection, no public code, no activation block, no miner support numbers — should flash red for anyone who remembers the “free money” fork cycle of 2017–2018. The cycle always goes the same way. First, excitement. Then, a handful of users claim the airdrop. Then, replay attackers drain them. Then, the fork coin trades at fractions of a penny until it is delisted.
The economic math is lopsided. Let’s say the fork gives you an equal number of fork coins for each BTC. Even if the fork coin somehow attains 1% of Bitcoin’s price, one BTC’s fork allocation is worth roughly $1,000 at current market ranges. Meanwhile, the mainnet BTC you might lose in a replay attack is full price. The expected value of claiming is negative. The only rational economic decision is not to claim. I don’t say that because I have a position against forks. I say it because I have watched this movie before. In 2020, I wrote about the Uniswap fork craze and the speed with which a governance loophole could turn into a front-running disaster. In 2022, I debated Terra’s “implicit peg” mechanics before the collapse. In both cases, the market’s narrative was ahead of its security. The same thing is happening here — except this time the market hasn’t even woken up to the narrative.
Third, the fork’s governance story is missing. Who is coordinating this? No GitHub organization. No documented code review. No audit. No transparent activation schedule. The only stakeholders who know anything are Ledger, because they test compatibility, and the fork developers themselves. Everyone else is in the dark. Audit passed? No. Audit existed? No. Logic flawed? Yes. There is no peer review for a chain that cannot name its own BIP correctly.
The BIP-110 naming issue also reveals something about the quality of the operation. Historical BIP-110 was implemented as part of the BIP-68/112/113 package. The real BIP-110 never proposed a separate chain. It proposed CHECKSEQUENCEVERIFY, a relative time lock that enables payment channels and other layer-two contracts. To use that number for a fork is like naming a new token “BTC-2010 hard fork” and hoping nobody checks the date. Either the fork designers made an embarrassing factual error, or they are deliberately borrowing the authority of an old BIP to give their chain a false pedigree. Both explanations should disqualify the project in the eyes of serious users.
Contrarian: The Real Danger Is Not Replay
Now for the angle nobody is covering. Ledger’s warning frames this as a replay protection bug. That framing is safe — and convenient. It positions the fork as a legitimate competing network that just needs a technical fix. I think that is wrong. I think the actual fork is not attempting an upgrade. It is attempting a rollback.
Consider what a chain without post-2016 soft forks would look like. No BIP-68 relative lock times. No BIP-112 CSV. No SegWit. No Taproot. This would be Bitcoin as it existed around 2015, before the scaling debates hardened into a governance settlement. A rollback fork like that does not need replay protection because it does not intend to survive. Its purpose is not to create value. Its purpose is to create chaos — to harvest the keys of users who think they are claiming free coins, and to delegitimize the consensus upgrades that Ledger and the wider ecosystem have already built on.
That changes the security calculus. You are not at risk only during the act of claiming. You are at risk from the moment you move any existing UTXO to a fresh address, if the chain is replayable. In fact, the safest possible move is to do absolutely nothing: no claiming, no splitting, no shuffling. But that is also exactly what the fork wants to avoid. It needs movement. It needs confusion. It needs users to fiddle with their hardware wallets while the mempool is loaded with identical raw transactions that attackers can shovel in either direction.
Even the market’s indifference plays into the wrong hands. Bitcoin spot ETFs and institutional custodians can ignore this fork because they have earned their position through regulation and process. Retail self-custody users cannot. They are the ones holding keys, and they are the ones who will be targeted. The asymmetry is brutal: institutions are watching, individuals are vulnerable, and the fork’s developers know it.
Let me be clearer about what I think is happening. A faction that politically opposes the soft fork direction of Bitcoin — SegWit, Taproot, the entire modern developer ecosystem — is threatening to run an old node version and produce a chain that shares Bitcoin’s history but not its upgrades. This is not a technical proposal. It is a political protest coded in block headers. And political protests are not subject to peer review, to BIP process, or to logical consistency. That is why the BIP number is wrong. That is why there is no replay protection. That is why Ledger had to issue a warning. The warning is accurate. The framework is a distraction.
Takeaway: The Winning Move Is Not to Play
A fork with no replay protection, no credible code, no economic engine, and a historically impossible BIP number should not get a place in your portfolio. It should not get a place in your horror stories either. The instructions are banal: do not claim, do not sign, do not move coins unless you have a trusted technical advisor who can split your UTXOs in a controlled environment. If the fork activates, the first 72 hours belong to arbitrage bots and replay attackers. Your Ledger will do exactly what you command, including signing a transaction that spends your mainnet BTC. It is not a guardian. It is a tool.
The market has learned to ignore fork narratives because every fork after Bitcoin Cash failed. But that institutional memory is exactly what this phantom chain is counting on. It is betting that you will be too bored to check whether the BIP number is real, too lazy to think about replay mechanics, and too greedy to resist a 1:1 airdrop. Don’t be.
Fork detected. Volatility imminent. Stablecoin algorithm failing? No. But run anyway: run away from the fork, toward the exit, with your keys untouched. And if you see a transaction that requests your “BIP-110 coins,” remember: that transaction is valid on every chain that still shares your history. Including the only chain that matters.