Ex-Ripple CTO: exchanges won't list Bitcoin forks due to security risks
- —Schwartz called replay protection the main condition for listing Bitcoin forks
- —Bitcoin Blake2b uses BLAKE2b instead of SHA-256 and shares transaction history with BTC
- —Coinbase, Kraken, and Trezor previously supported Bitcoin Cash but ignore Blake2b
- —Without protection, transactions can be duplicated between chains and lead to loss of funds
Why it matters: The dispute sets a standard for listing new forks: without verifiable replay protection, exchanges will not take on the risk of losing customer funds.
Source: Digital Today