Coinbase said on November 13, 2018 that it would halt all Bitcoin Cash buys, sells, trading, deposits and withdrawals while the network attempted a contested protocol upgrade two days later. The decision widened an earlier plan that covered only sends and receives, turning the approaching fork into a market-access event for both retail and institutional customers.
The suspension was scheduled to begin at 8:00 a.m. Pacific Standard Time on November 15 across Coinbase.com, its mobile applications, Coinbase Pro and Coinbase Prime. Transfers were also to stop at Coinbase Custody. Coinbase characterized that start time as approximately one hour before the expected fork, while emphasizing that it did not control the network’s actual timing.
The verified development was Coinbase’s operating decision, not the outcome of the fork. As of November 13, the exchange said it could not predict whether one or two viable chains would remain.
From wallet precautions to a market shutdown
Coinbase planned to take a snapshot of customer BCH balances after services stopped, monitor the network for consensus and clear the Pro and Prime order books before trading eventually resumed. It gave no fixed duration for the interruption. Restoring service would depend on Coinbase determining that network conditions had stabilized and met its security standards.
That sequence mattered because a hard fork can leave exchanges deciding which software rules, ledger and asset symbol their systems recognize. When competing chains share a transaction history, custody providers must also determine how balances on any surviving alternative chain will be handled. Coinbase said that if another viable chain persisted, customers would eventually be able to withdraw the corresponding funds, but warned that the work could take weeks or longer.
Other venues adopted materially different policies. Kraken’s November 10 notice said it expected the upgrade at about 16:40 UTC on November 15, defined technically by the median time past of the preceding 11 blocks reaching Unix timestamp 1542300000. Kraken planned to stop BCH funding approximately 60 minutes beforehand but continue trading, initially treating the Bitcoin ABC network as BCH. Bitfinex planned to suspend deposits and withdrawals at 15:30 UTC, snapshot balances at 16:40 UTC and avoid endorsing either competing proposal.
The contrast showed that there was no industry-wide procedure for a disputed fork. Access, ticker treatment and entitlement to a possible second asset depended partly on each intermediary’s custody and listing policy.
The protocol dispute behind the controls
A contemporaneous Bitwise research note described Bitcoin ABC’s planned changes as including canonical transaction ordering and two new scripting operations, OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY. Canonical ordering was intended to support future block-propagation improvements, while the new operations could verify that a message, signature and public key matched.
Bitcoin SV opposed the ABC roadmap and offered an incompatible implementation. Kraken identified it as the principal rival proposal and said on November 10 that it did not then meet Kraken’s listing requirements. These were competing software and policy positions known before activation; neither established on November 13 which chain would attract sufficient mining, economic or infrastructure support.
What remained unresolved
Coinbase’s halt reduced immediate execution and transfer risk on its own systems, but it could not resolve the underlying coordination problem. Miners could redirect computing power, node operators could choose incompatible rules, and exchanges could assign the BCH symbol differently. A balance snapshot documented customer holdings at one venue; it did not determine the market value, liquidity or long-term viability of assets on either prospective chain.
No defensible event-day conclusion could declare a winner or assume that both chains would survive. The importance of November 13 was narrower: a major exchange judged the uncertainty serious enough to progress from a wallet freeze to a complete BCH market pause, while rival venues disclosed different approaches. The episode exposed how decentralized protocol disputes could produce centralized decisions about trading access, custody and asset identity.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.