Bitcoin replay attack concerns grow amid BIP-110 hard fork discussions

Supporters of the BIP-110 proposal are discussing a potential hard fork to address replay attack risks. The proposed move involves replacing the minority chain’s SHA-256d mining algorithm with BLAKE2b, which would create a distinct design while maintaining shared transaction history prior to the split.

A replay attack occurs when a transaction intended for one blockchain can be copied and broadcast onto another because both networks recognize the same signature rules. This allows a party to re-execute a valid authorization on a different chain without needing the user's private key.

Luke Dashjr has criticized Bitcoin, referring to it as ‘Spamcoin,’ and has advocated for improved replay protection. Developers have noted that a significant portion of blocks on the BIP-110 minority chain consist of replayed transactions from the main chain. While Bitcoin Knots is planning a new sighash to mitigate this, certain replay protections may remain opt-in.