The Bitcoin Cash chain split: 1 August 2017, block 478,559
Bitcoin and Bitcoin Cash were one chain until block 478,558. On 1 August 2017 nodes running the Bitcoin Cash rules began accepting blocks larger than one megabyte, and from the next block on there were two chains with one shared history. This is the record of that split: the dispute, the rule change, the blocks, the names and the balances.
When did the BTC / BCH split happen?
On 1 August 2017. The two chains share every block up to 478,558, timestamped 13:16 UTC that day. The next block, 478,559, exists twice: Bitcoin's was timestamped 13:23 UTC, Bitcoin Cash's 18:12 UTC, mined by ViaBTC and 1.9 MB in size, which the old 1 MB limit did not allow. The split came from a rule change that raised the block-size limit to 8 MB and added replay protection. Every coin held at block 478,558 stayed spendable on both chains, one for one.
| The split | Bitcoin (BTC) | Bitcoin Cash (BCH) |
|---|---|---|
| Last shared block | 478,558, timestamped 1 August 2017 13:16:14 UTC | |
| Activation | Bitcoin Cash rules active once the median time of the last 11 blocks reached 12:20 UTC on 1 August 2017 | |
| First block after the split | 478,559, 13:23:00 UTC, 272,502 bytes | 478,559, 18:12:41 UTC, 1,915,175 bytes, 6,985 transactions, mined by ViaBTC |
| Rule change | None: kept the 1 MB limit | Block-size limit 8 MB, first block required to exceed 1 MB, new signature rule (SIGHASH_FORKID) |
| Balances | Every coin unspent at block 478,558 spendable on both chains, 1:1 | |
| Name and ticker | Bitcoin, BTC | Bitcoin Cash, BCH (first listed as BCC) |
Why the chain split
Bitcoin had carried a 1 MB limit on block size since 2010. By 2017 blocks were full often enough that fees and waiting times rose, and the network had argued for years over what to do. One side wanted to raise the limit and keep payments on the chain itself. The other preferred to keep the base block small, move signature data out of it with Segregated Witness (SegWit, BIP 141), and carry more payments on second-layer systems. Neither side could bring the other round. The Bitcoin Cash website, as quoted at the time, put it this way: “the community could not reach a consensus, even after years of debate.”
Bitcoin ABC, a node client led by Amaury Séchet, wrote the rules for raising the limit as a hard fork: the user-activated hard fork, or UAHF, specified in July 2017. The mining pool ViaBTC announced support and named the result Bitcoin Cash. SegWit was already on its way to activation on the other side, and it activated on Bitcoin on 24 August 2017, at block 481,824. The two changes could not run on the same chain, so each group of nodes kept its own. The site's two upgrade paths of 2017 covers what each path changed and why the naming that followed is a choice, not a fact about either chain.
The rule change
The UAHF specification (version 1.6, dated 24 July 2017) set four rules that mattered for the split:
- Activation by time. The new rules applied once the median time of the last 11 blocks reached Unix time 1501590000, 12:20 UTC on 1 August 2017. Block 478,558 was the first whose median time passed it, so block 478,559 was the first under the new rules.
- A larger limit. Blocks of up to 8,000,000 bytes became valid, with a cap of 20,000 signature operations per megabyte.
- A forced first block. The fork block itself had to be larger than 1,000,000 bytes. That made the split immediate: the first Bitcoin Cash block was invalid to every node still running the old rules, and the first Bitcoin block after 478,558 was too small to be valid to Bitcoin Cash nodes.
- Replay protection. Every Bitcoin Cash transaction had to sign with a new flag, SIGHASH_FORKID (0x40), over a revised signature hash. A transaction signed for one chain was invalid on the other.
The same specification added an emergency difficulty adjustment (EDA): if six blocks took 12 hours or more, the difficulty fell by 20%. Bitcoin Cash began at Bitcoin's difficulty with a small share of the hashpower, and the rule was there so that the chain would not stall. It was replaced on 13 November 2017 by a difficulty algorithm that averages over about 144 blocks.
The blocks: 478,558 and two 478,559s
Block 478,558 is the last block the two chains have in common. Its header is timestamped 13:16:14 UTC on 1 August 2017, and its median time, 12:37:28 UTC, was past the activation point. Seven minutes later Bitcoin had its block 478,559, at 272,502 bytes. Bitcoin Cash's block 478,559 is timestamped 18:12:41 UTC, almost five hours after Bitcoin's. ViaBTC mined it: 1,915,175 bytes and 6,985 transactions, with the coinbase message “Welcome to the world, Shuya Yang!”. The gap follows from the arithmetic: both blocks carry the same difficulty target, and the Bitcoin Cash side had only a small share of the hashpower to meet it.
Header times are set by the miner and can be off by minutes; the block heights and the order are exact. From block 478,559 onward each chain has its own blocks, and a block on one is not a block on the other.
Which side kept which name
The chain that kept the 1 MB limit kept the name Bitcoin and the ticker BTC. The chain that raised it took the name ViaBTC had given it, Bitcoin Cash. ViaBTC's market listed it as BCC before the split, a ticker the BitConnect token already used on many exchanges; BCH became the common ticker for Bitcoin Cash.
Which branch is the original is a label, not a property either chain has. Both start from the genesis block of 3 January 2009 and both carry the same history to block 478,558. One has the name and the larger market; the other kept the path of raising the block-size limit. Hard fork vs chain split covers the mechanism behind that: a rule change without enough agreement leaves two chains.
How balances carried over
Nothing was sent to anyone. Every coin unspent at block 478,558 was in the history of both chains, so whoever held a coin before the split could spend it on either afterwards: one BTC and one BCH for every bitcoin held. Because Bitcoin Cash transactions had to sign with SIGHASH_FORKID, spending on one chain did not spend on the other. That let holders move their coins on each chain separately, without first splitting them by hand.
Coins held on exchanges were credited at the exchanges' own pace. Coinbase first said it would not support Bitcoin Cash, reversed that within days, and on 19 December 2017 opened BCH trading and credited each customer with Bitcoin Cash equal to their bitcoin balance at the time of the split. The site does not count these balances as an airdrop to either side: both chains carry the same coins up to the split, and every coin on either chain was mined, before the split or after it.
Where each chain stands now
Both chains still run SHA-256 proof of work with a ten-minute block target and a 21 million cap, and since 1 August 2017 each has changed its rules on its own.
Bitcoin activated SegWit on 24 August 2017 and Taproot in 2021. Its base block limit is still 1 MB, with witness data counted separately under a block weight limit.
Bitcoin Cash has upgraded on a schedule, usually every 15 May and, until 2020, every 15 November:
- 15 May 2018: block-size limit raised to 32 MB, and several original script opcodes re-enabled.
- 15 November 2018: canonical transaction ordering and OP_CHECKDATASIG. The dispute over this upgrade split the chain again: see the Bitcoin SV chain split.
- 2019: Schnorr signatures (May) and Schnorr multisig (November).
- 15 November 2020: a new difficulty algorithm, ASERT. Bitcoin ABC's extra coinbase rule in the same upgrade split off a third chain: see the eCash chain split.
- 15 May 2023: CashTokens, native fungible and non-fungible tokens (CHIP-2022-02).
- 15 May 2024: an adaptive block-size limit (ABLA, CHIP-2023-04) that grows with use and never falls below 32 MB.
- 15 May 2025: targeted virtual machine limits and high-precision arithmetic (BigInt).
- 15 May 2026: pay-to-script, bounded loops, functions and re-enabled bitwise operations.
Price, market cap, hashrate and rank move every few hours; they are on the Bitcoin and Bitcoin Cash asset pages. The site counts both as cryptocurrencies, because each has its own chain and its own consensus: why BTC, BCH and BSV are three cryptocurrencies.
Sources
- Bitcoin ABC, UAHF technical specification, version 1.6, 24 July 2017 (REQ-2 activation, REQ-3 fork block, REQ-4 block size, REQ-6 SIGHASH_FORKID, REQ-7 EDA).
- November 13, 2017 upgrade specification (difficulty adjustment algorithm).
- Bitcoin Cash upgrade specifications: May 2018, November 2018, November 2020, May 2023, May 2024, May 2025, May 2026.
- CHIP-2023-04, Adaptive Blocksize Limit Algorithm for Bitcoin Cash (32 MB floor).
- Block data: Bitcoin blocks 478,557 to 478,559 from mempool.space; Bitcoin Cash block 478,559 from Blockchair; read 16 November 2026.
- Brave New Coin, ViaBTC plans to launch Bitcoin alternative, 'Bitcoin Cash', on August 1st, 25 July 2017.
- TechCrunch, Coinbase now lets you buy and sell Bitcoin Cash, 19 December 2017; Coinbase, What is Bitcoin Cash?