Bitcoin Forks Struggle to Clear Exchange Hurdles as Former Ripple CTO Highlights Security Concerns

Major cryptocurrency exchanges are hesitating to list Bitcoin-related assets, according to former Ripple chief technology officer (CTO) David Schwartz. Speaking to the blockchain media outlet U.Today on September 18 (local time), Schwartz noted that platforms like Coinbase must prioritize examining safety measures such as replay protection to prevent duplicate transactions across different chains.
The debate began when an X (formerly Twitter) user questioned why Bitcoin Blake2b—a fork of Bitcoin—was being overlooked by exchanges, despite Coinbase, Kraken, and Treasure having previously supported other Bitcoin forks like Bitcoin Cash. While older Bitcoin forks were accessible on these platforms, users could continue trading them.
Bitcoin Blake2b is a separate chain that diverged from Bitcoin, using the Blake2b mining algorithm instead of Bitcoin's SHA-256. Its structure shares transaction history with Bitcoin before separation, which has sparked controversy.
Schwartz argued this structure could pose fund protection issues for exchanges. He stated that when handling newly split assets, exchanges should adopt replay protection mechanisms to address potential vulnerabilities. The shared transaction history between Bitcoin and the new fork network raises concerns about engineering flaws that might lead to user fund loss.
The core issue is preventing transactions initiated on one chain from being unintentionally processed on another. Schwartz emphasized that for security, exchanges must implement sufficient safeguards like replay protection to ensure transactions on a new chain do not get reprocessed on the original chain.
Market reactions suggest this discussion highlights technical stability and operational burden rather than simple listing criteria. The fact that previous Bitcoin forks were supported does not automatically justify applying the same standard to newer chains.
The differing responses from exchanges versus wallet providers have also come under scrutiny. While Bitcoin Blake2b-based chains are receiving different treatment compared to older fork assets, users have raised concerns about this disparity. However, the debate ultimately centers on whether listing decisions will be tied directly to technical risk management.
Key focus moving forward is whether the Bitcoin Blake2b community can clearly demonstrate security measures that exchanges require. The presence of critical safety features like replay protection and whether exchanges can sufficiently verify them will likely determine listing discussions.
"Robust replay protection is widely considered a technical prerequisite for listing a newly-split asset. These policies were generally adhered to in previous BTC forks. No exchange wants to deal with customers screwing up deposits due to poor engineering on a minor fork," Schwartz wrote on X (formerly Twitter) on September 18, 2026.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 거래소 문턱 못 넘는 비트코인 포크…리플 전 CTO "보안이 관건"