Bitcoin Hard Forks: Your Coins Might Be Copied
Supporters of BIP-110 are preparing a hard fork—switching the mining algorithm of the minority chain from SHA-256d to BLAKE2b. This brings the old problem back into the spotlight: replay attacks.
In plain terms: after the fork, both chains share the transaction history that existed before the split. If you send a transaction on the old chain, the same signature is also valid on the new chain. Someone can copy the transaction exactly, broadcast it to the new chain, and your coins will be passively copied away.
It’s not that the private keys were stolen. It’s not that cryptography was broken. It’s simply that an authorization is recognized by both chains—you can’t really stop it.
On August 18, Dashjr said replay protection is the responsibility of Spamcoin. He calls the mainstream chain Spamcoin and even insults it as a clone coin. But the data contradicts him: the peak support rate among BIP-110 miners was only 2.53%. After the consensus rules took effect on August 8, the minority chain produced just two blocks before going offline.
Mempool developer Mononaut complained that those minority-chain blocks were mostly just replaying old transactions from days earlier on the main chain. The “new world” promised turned out to be a copy machine.
My take: when it comes to forks, the replay protection that ordinary people are most likely to overlook. Coins are fine on exchanges, but if you hold them in your own wallet, take extra care—don’t wait until your balance is short to figure out what happened.
How do you think this fiasco will end? Discuss it in the comments.
Click the avatar to watch the livestream.
Every day, I’ll help you track Bitcoin trends—not just what’s happening in the news, but also the logic and opportunities behind it 👉🦖
#比特币 #BIP110
Supporters of BIP-110 are preparing a hard fork—switching the mining algorithm of the minority chain from SHA-256d to BLAKE2b. This brings the old problem back into the spotlight: replay attacks.
In plain terms: after the fork, both chains share the transaction history that existed before the split. If you send a transaction on the old chain, the same signature is also valid on the new chain. Someone can copy the transaction exactly, broadcast it to the new chain, and your coins will be passively copied away.
It’s not that the private keys were stolen. It’s not that cryptography was broken. It’s simply that an authorization is recognized by both chains—you can’t really stop it.
On August 18, Dashjr said replay protection is the responsibility of Spamcoin. He calls the mainstream chain Spamcoin and even insults it as a clone coin. But the data contradicts him: the peak support rate among BIP-110 miners was only 2.53%. After the consensus rules took effect on August 8, the minority chain produced just two blocks before going offline.
Mempool developer Mononaut complained that those minority-chain blocks were mostly just replaying old transactions from days earlier on the main chain. The “new world” promised turned out to be a copy machine.
My take: when it comes to forks, the replay protection that ordinary people are most likely to overlook. Coins are fine on exchanges, but if you hold them in your own wallet, take extra care—don’t wait until your balance is short to figure out what happened.
How do you think this fiasco will end? Discuss it in the comments.
Click the avatar to watch the livestream.
Every day, I’ll help you track Bitcoin trends—not just what’s happening in the news, but also the logic and opportunities behind it 👉🦖
#比特币 #BIP110