TL;DR
- David Schwartz linked exchange hesitation around Bitcoin BLAKE2b to technical and security requirements rather than simple market demand.
- The network switched Bitcoin’s SHA-256d proof of work to BLAKE2b, with its first block mined at height 961,640 on August 30, 2026.
- Smaller platforms already offer trading for the asset, while larger exchanges continue to evaluate the infrastructure and security requirements involved.
Ripple CTO Emeritus David Schwartz has offered a technical explanation for why major exchanges have been cautious about listing Bitcoin BLAKE2b, a Bitcoin-derived network that uses BLAKE2b proof of work instead of Bitcoin’s SHA-256d. The debate centers on why some older Bitcoin forks received exchange support while this newer asset faces a more limited rollout.
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.
— David ‘JoelKatz’ Schwartz (@JoelKatz) September 18, 2026
The issue gained attention after users questioned the absence of Bitcoin BLAKE2b from platforms such as Coinbase and Kraken, while Bitcoin Cash and Bitcoin SV had previously secured exchange markets. Bitcoin BLAKE2b launched its first BLAKE2b block at height 961,640 on August 30, 2026, creating a separate chain that retained Bitcoin’s earlier transaction history.
Bitcoin BLAKE2b Faces Exchange-Level Technical Questions
Schwartz suggested that the hesitation may be connected to engineering and security requirements rather than simply a lack of market interest. A fork can share transaction history with the original Bitcoin chain, creating situations in which poorly handled transactions could be replayed across networks. Exchanges therefore need safeguards that separate deposits, withdrawals and transaction validity on each chain.
Replay protection is particularly important for custodians because an operational mistake can affect many users at once. Listing a fork also requires infrastructure teams to review node software, wallet compatibility, confirmations and monitoring before opening deposits and withdrawals.
Bitcoin BLAKE2b changes the proof-of-work algorithm from SHA-256d to BLAKE2b. Miners using Bitcoin’s conventional algorithm therefore cannot simply continue producing blocks on the new chain. The project’s documentation identifies block 961,640 as the first BLAKE2b block and describes temporary restrictions on arbitrary data storage during the network’s initial period.
Exchange Access Could Expand As Infrastructure Matures
The asset is already tradable on smaller venues. Current market data shows Bitcoin BLAKE2b trading under tickers including BTCB2 and XBT, with markets on platforms such as NonKYC and SafeTrade. That gives the network an early liquidity layer, although volumes remain limited compared with established cryptocurrencies.
For larger exchanges, the technical burden can be more significant than simply adding a new trading pair. Coinbase says asset reviews include business criteria and due diligence before an asset can move toward broader platform support. That helps explain why a technically distinct Bitcoin fork may require additional infrastructure work despite sharing Bitcoin’s earlier history.
Be the first to comment