Bitcoin ABC released version 0.18.3 of its Bitcoin Cash node software on November 10, 2018, adding operational and performance tools five days before a scheduled protocol upgrade that exchanges warned could produce multiple viable chains.
The official Bitcoin ABC download archive timestamps the 0.18.3 directory at 13:08 on November 10. Surviving release notes describe a broad maintenance release rather than a new consensus proposal. Its additions included commands for parking and unparking blocks, a corresponding “parked” state in the chain-tip interface, fuller block-transaction retrieval, improved SHA-256 performance on supported processors and assorted stability fixes.
Maintenance software entered an exceptional environment
The distinction between software maintenance and consensus rules is important. Bitcoin ABC 0.18.3 did not originate the November 15 upgrade. Bitcoin ABC had placed those consensus changes in version 0.18.0 on August 20, 2018 and told operators to upgrade before activation.
That earlier specification included canonical transaction ordering and `OP_CHECKDATASIG`, an opcode intended to let scripts validate messages originating outside the blockchain. Bitcoin ABC presented canonical ordering as groundwork for future scaling and the opcode as infrastructure for applications such as oracles and cross-chain atomic contracts. Those were the developer group’s stated purposes, not demonstrated event-day outcomes.
Features such as `parkblock` and `unparkblock` gave node operators additional control over which chain tips their software followed. The release notes do not say those commands were created specifically for the impending dispute, however, and this reconstruction does not assign that motive. Their significance on November 10 came from the operating environment into which they were released.
Kraken selected Bitcoin ABC for its BCH markets
Kraken announced its own policy on November 10. The exchange said it would initially support only Bitcoin ABC and would configure its Bitcoin Cash wallets accordingly after the scheduled change. BCH trading would continue, but deposits and withdrawals were to stop approximately 60 minutes before the expected November 15 activation.
Kraken identified Bitcoin SV, proposed by nChain, as Bitcoin ABC’s principal rival. It warned that the upgrade was more controversial than previous Bitcoin Cash changes and might leave more than one viable chain. The exchange made no promise to support an alternative asset and cautioned that customers leaving BCH on the platform could forfeit access to coins on unsupported branches.
That was an exchange custody and naming decision—not a protocol vote capable of determining which rules miners, businesses or independent node operators would adopt. It nevertheless mattered because centralized venues controlled customer balances, deposit addresses and the symbols displayed on their order books.
BCH carried a visible fork premium
CoinMarketCap’s historical snapshot for November 10 placed Bitcoin Cash fourth among tracked cryptocurrencies at $556.50, with reported market capitalization of $9.71 billion and reported 24-hour volume of $656.84 million. The snapshot showed BCH up 2.29% over 24 hours and 14.20% over seven days.
Bitcoin appeared at $6,409.22, up 0.25% over 24 hours and 0.75% over seven days. BCH’s relative strength was therefore conspicuous, but the data do not establish that the software release or Kraken notice caused it. The figures are aggregator snapshots across continuously traded venues, not official closing prices, audited worldwide turnover or measurements of new capital entering the market.
What remained unresolved on November 10
The verifiable event-day record showed three things: Bitcoin ABC had refreshed its production node software, its planned consensus rules were scheduled for November 15, and Kraken was preparing for incompatible chains rather than assuming an uncontested upgrade.
The record did not yet establish which implementation would attract more hashpower, whether two chains would persist, what tickers other exchanges would assign or how customer assets would ultimately be handled. Those outcomes were unknowable on November 10 and are not projected backward into this reconstruction.
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.