The Bitcoin Diamond chain split: block 495,866, 24 November 2017
Bitcoin Diamond did not come out of a quarrel among Bitcoin's own nodes. A team announced it two days ahead, copied Bitcoin's ledger at a fixed height, multiplied every balance by ten and started a new chain with a different proof of work. It traded on large exchanges for four years. The record of the chain itself is thinner than for any other split on this site, and this post says where it runs out.
What was the Bitcoin Diamond fork?
A copy of Bitcoin's ledger taken at block 495,866, mined at 09:20 UTC on 24 November 2017, continued as a separate chain from block 495,867. Every bitcoin became ten BCD. The new chain replaced SHA-256 with a variant of the X13 algorithm, allowed blocks eight times larger, retargeted difficulty every 72 blocks and made replay protection mandatory. Its code also paid 14 million BCD to the miner of its first block. Bitcoin kept its name and ticker; the new chain was Bitcoin Diamond, BCD. Its last node release dates from May 2019, the major exchanges dropped it in 2022, and no explorer that still answers shows the chain producing blocks.
| Last shared block | 495,866, 24 November 2017, 09:20 UTC |
|---|---|
| First Bitcoin Diamond block | 495,867; its time is not published by any explorer that still answers |
| Rule change | X13 proof of work with SM3 in place of Luffa; blocks up to 32 million weight units; retarget every 72 blocks; a new transaction format |
| Balances | 10 BCD per BTC at block 495,866, plus 14,000,000 BCD paid to the first block |
| Replay protection | Mandatory: every transaction carries a recent block hash and a new version number |
| Tickers | Bitcoin (BTC) unchanged; Bitcoin Diamond (BCD) on the new chain |
Why it was made: what the project said, and what critics said
Bitcoin Cash split in August 2017 because part of Bitcoin's own network chose to raise the base block size rather than take the SegWit path. Bitcoin Diamond had no such constituency. It was one of several forks of late 2017, after Bitcoin Gold, built by a new team on a copy of the ledger. Its site named two development teams, "EVEY" and "007", and a Bitcoin Diamond Foundation. The project described BCD as "a free dividend for BTC holders" and said it was not a competitor of Bitcoin.
The problems it said it would solve were slow confirmations, high fees and a "high threshold for new members", the last answered by the tenfold coin count, which made each coin cheaper. The plan was 8 MB base blocks with SegWit, a GPU-mineable algorithm instead of SHA-256 ASICs, and Lightning Network support in 2018. The team published a fork of c-lightning in July 2018.
Contemporary reporting was sceptical. On 25 November 2017 David Gerard noted that the project's GitHub link led nowhere and that its developers were listed only as "007", "Evey" and "?". CriptoNoticias reported warnings that the fork had no blockchain or code of its own. Cointelegraph described an anonymous team and foundation, and printed figures, 4.2 billion coins and a move to proof of stake after 10,000 blocks, that the code later published does not bear out. The public node repository was created on 20 December 2017, almost four weeks after the snapshot; its first tagged release, 1.0.0 RC1, came on 8 January 2018.
The rule change, from the code
The node source, eveybcd/BitcoinDiamond, sets the fork height at 495,867. From that block a valid block must set a version bit, 0x40000000, and meet a proof of work computed with X13sm3: the thirteen hash functions of X13 with China's SM3 standard in place of Luffa. Blocks without the bit are rejected, and so is every block that uses Bitcoin's SHA-256 proof of work. The first block was allowed at the minimum difficulty.
The other changes follow from a small, new network. Difficulty retargets every 72 blocks, about twelve hours, by at most a factor of two each time, instead of every 2,016 blocks. The block weight limit is 32 million units, eight times Bitcoin's. The target interval stays at ten minutes and the halving interval at 210,000 blocks. Addresses use Bitcoin's prefixes, so the same keys control both balances.
Replay protection is built into the transaction format. Every transaction in a Bitcoin Diamond block, except the coinbase, must use a new version number and carry the hash of a recent block, and that hash is part of what the signature covers. A transaction signed for Bitcoin is not valid on Bitcoin Diamond, and the reverse.
How balances carried over, and the 14 million coins
The tenfold balance is done with decimals rather than arithmetic. Bitcoin counts a coin in 100 million satoshis; Bitcoin Diamond counts a coin in 10 million base units. Each satoshi at block 495,866 became one base unit, so 1 BTC became 10 BCD. The block reward is ten times Bitcoin's on the same halving heights: 125 BCD at the fork, 62.5 from block 630,000 and 31.25 from block 840,000. Bitcoin's ledger at the snapshot comes to about 167 million BCD.
One block breaks the pattern. The subsidy function returns 14,000,000 BCD for block 495,867, the first block on the new chain. The project's site never called this a premine, but its Bitcoin Diamond Foundation table allotted 2% of supply to start-up and operations and 4.6% to development and the ecosystem, time-locked at 20% a year: 6.6% of 210 million is 13.9 million, close to the size of that first block. Who mined the block is not on any explorer that still answers.
The site gave the total supply as 210 million: 170 million for Bitcoin holders and 40 million for "the community rewards pool as tributes and mining". The code does not match it. Ten times Bitcoin's schedule already reaches 210 million, so the 14 million first block puts the ceiling the code allows at about 224 million.
Exchanges then and later
Binance announced on 24 November 2017 that it would snapshot BTC balances at block 495,866 and credit 10 BCD per BTC once the new chain and wallet proved "usable and stable", adding that "the default position we have is no listing". BCD was later credited and traded there, but Binance kept deposits and withdrawals closed until September 2018, so for most of a year Binance's BCD could not leave Binance. KuCoin opened BCD/BTC and BCD/ETH markets on 26 November 2017.
The large venues left in 2022. Binance delisted BCD on 8 March 2022 and allowed withdrawals until 9 June. KuCoin removed BCD/BTC and BCD/ETH on 28 December 2022 under its special treatment rules, with withdrawals until 28 June 2023. Neither gave a reason specific to BCD; Binance's list of review criteria includes development activity and network stability.
Where the chain stands
The node has not changed since 2019. Its last release, 1.3.0, came on 15 May 2019, and the last commit to the repository in April that year. A Go implementation from the same organisation stopped in March 2020. Two Bitcoin Core vulnerabilities disclosed in July 2024, an orphan-transaction stall and an unbounded ban list, remain in 1.3.0.
Whether the chain still makes blocks cannot be confirmed from anything public. Checked on 16 November 2026: bitcoindiamond.org refuses connections, and the Internet Archive's last copy is from April 2025. The btcd.io domain, which hosted the official explorer, and all six DNS seeds hard-coded in the node, now resolve to the same parked addresses; the explorer last appears in the archive in October 2025. Tokenview, once a BCD explorer, returns no data. WhatToMine lists a last block of 826,002 at 62.5 BCD a block, without a date, and marks the coin as lagging. No source that answered shows a block after it, or a date for it. Any market data is on the Bitcoin Diamond asset page.
What the counting rule makes of it
The site counts a split chain as a cryptocurrency when it has its own blockchain and its own consensus. Bitcoin Diamond met both from block 495,867: a different proof of work and rules no Bitcoin node accepts. The rule also depends on the chain continuing. A chain that no miner extends is not one the rule can find, as Hard fork vs chain split sets out, and Bitcoin Diamond's continuation is exactly what no public source can show today. Bitcoin is unaffected: its chain never accepted a Bitcoin Diamond block.
Sources
- Bitcoin Diamond node source, eveybcd/BitcoinDiamond: chainparams.cpp (fork height, first-block reward, seeds, prefixes),
src/validate/validate_block.cpp(subsidy),src/pow.cpp(72-block retarget),src/hash.h(X13sm3),src/amount.h(decimals),src/consensus/consensus.h(block weight),src/consensus/tx_verify.cpp(replay protection); releases 1.0.0 RC1 to 1.3.0, read 16 November 2026. - Bitcoin Diamond, About, FAQ, foundation table and roadmap, archived copy of bitcoindiamond.org.
- Bitcoin block 495,866: mempool.space.
- David Gerard, News: Bitcoin Diamond, 25 November 2017; CriptoNoticias; Cointelegraph, 24 November 2017.
- Binance's statement on Bitcoin Diamond, 24 November 2017, as quoted on bitcointalk; Investing.com, 5 September 2018.
- KuCoin, listing, 26 November 2017, and delisting, 23 December 2022; Binance, Binance Will Delist BCD, CND, MTH, NCASH and YOYO, 1 March 2022.
- Bitcoin Core disclosures of 3 July 2024: orphan handling and unbounded ban list.
- Network status checked 16 November 2026: bitcoindiamond.org, explorer.btcd.io and the node's DNS seeds; Tokenview; WhatToMine; Internet Archive captures of bitcoindiamond.org and explorer.btcd.io.