Exchanges froze Bitcoin Cash transfers ahead of a disputed network fork

Bitstamp disabled Bitcoin Cash deposits and withdrawals at 12:00 UTC on November 14, 2020, beginning an operational lockdown ahead of a disputed network upgrade scheduled for November 15. Bittrex planned to close its BCH wallets eight hours later, at 20:00 UTC, while keeping trading available. These restrictions turned a disagreement among software developers and miners into an immediate custody and market-access issue for exchange customers.

The interruption mattered because Bitcoin Cash was not a marginal asset. CoinMarketCap’s November 14 historical snapshot ranked BCH sixth among tracked crypto assets, with an indicated price of $255.77, circulating supply of 18,572,188 BCH and market capitalization of approximately $4.75 billion. Its reported 24-hour volume was about $2.13 billion. Those figures describe CoinMarketCap’s aggregated snapshot—not a universal closing price or the value available for execution on every venue.

Two incompatible rule sets

The scheduled activation was tied to the median time past of the most recent 11 blocks reaching Unix timestamp 1605441600, corresponding to November 15 at 12:00 UTC. The Bitcoin Cash Node specification replaced the existing difficulty-adjustment system with ASERT, an algorithm intended to keep block production closer to its target when mining power moved in or out of the network.

Bitcoin ABC planned a different implementation. Its August 24 statement said its upgrade would require a percentage of each new block reward to be directed to an infrastructure fund. Bitstamp characterized that provision as a developer tax. Bitcoin Cash Node’s published specification did not include the funding rule, leaving the clients unable to follow the same consensus rules after activation if both attracted miners.

A permanent split was possible but had not occurred on November 14. Hashpower signaling cited by exchanges favored Bitcoin Cash Node, yet signaling was an indicator rather than a binding vote or guarantee of the blocks miners would produce after activation. The eventual survival, naming and market support of either resulting chain therefore remained uncertain in the event-day record.

Why exchanges restricted transfers

For custodial venues, uncertainty extended beyond which software would attract more mining power. A chain split could create two ledgers sharing the same transaction history through the final common block. Exchanges then had to determine which ledger would retain the BCH ticker, whether customers would receive an additional asset and when deposits could be credited without ambiguity.

Bitstamp said it would take a balance snapshot before the fork and expected the Bitcoin Cash Node chain to remain BCH if it emerged as dominant. It reserved judgment if two viable chains survived. Bittrex similarly planned to assign the BCH name to the chain with the most mining-pool support and evaluate the competing asset separately. Its notice warned that incorrectly submitted cross-chain deposits would not be recovered because of the anticipated replay-protection problem.

The policies also demonstrated the difference between owning an asset through an intermediary and controlling its private keys. During the suspension, customers could still have an account balance while being unable to move the underlying BCH on-chain. Whether they would receive access to coins on both possible ledgers depended on each venue’s snapshot, custody and listing policies.

What was known on November 14

The verified development was the start of exchange transfer restrictions, not the fork’s outcome. The available records established the activation rules, competing implementations and venue contingency plans. They did not establish that two durable networks would result, which chain would retain economic dominance, or what either asset would be worth afterward. CoinMarketCap’s 1.31% reported 24-hour decline for BCH was contemporaneous market context, but it does not prove that fork preparations caused the move.