Learn
What is BitcoinII?
BitcoinII (BC2) is Bitcoin’s design on a new network. Its whitepaper calls it “a faithful re-deployment of the original protocol”: the same monetary rules and SHA-256 proof of work, started from a clean genesis block with no premine.
BC2 addresses look identical to Bitcoin addresses. Always confirm the network before sending. BC2 is not BTC: don’t send BTC to a BC2 address, or BC2 to a BTC address.
Where it came from
- Dec 12, 2024: the genesis block (block 0) was created. Its hash is
0000000028f062b221c1a8a5cf0244b1627315f7aa5b775b931cfec46dc17ceb. - June 22, 2025: test mining began (block 1).
- July 2, 2025: open public mining began with the BitcoinTalk announcement. How it launched.
- Aug 18, 2025: the whitepaper was published.
- Aug 29, 2026: block 57,750 activated ShockWave, the data limits and replay protection (BitcoinII Core v31.1.0).
The whitepaper describes BitcoinII as “a second chance for those who missed Bitcoin’s earliest days”. That is about timing: the chance to run a node, mine and take part while a Bitcoin-style network is young.
The monetary rules
- Maximum supply
- 21,000,000 BC2
- Block time
- Targets 10-minute blocks; actual intervals vary with hashrate
- Block subsidy
- 50 BC2
- Halving
- Every 210,000 blocks; the first is at block 210,000
- Proof of work
- SHA-256 (SHA-256d)
- Software
- Based on Bitcoin Core v31.1; SegWit and Taproot supported
Technology
- SegWit and Taproot have been active since the network’s first few hundred blocks (SegWit from block 290, Taproot from block 300).
- Same consensus rules and tools as Bitcoin, with the BC2-specific changes listed below.
- No merged mining. SHA-256 hashrate goes to BitcoinII or to Bitcoin, not both at once. BitcoinII Core can run alongside Bitcoin Core on the same machine, with separate data directories and ports.
Issuance at a glance
| BitcoinII (BC2) | Bitcoin (BTC) | |
|---|---|---|
| Maximum supply | 21,000,000 | 21,000,000 |
| Launched | Dec 2024 (genesis) | Jan 2009 |
| Current block subsidy | 50 BC2 | 3.125 BTC |
| Next halving | Block 210,000 | — |
| Share of the 21 million cap issued | — (from the live block height) | — |
With JavaScript on, the share of the cap is worked out from the block height on explorer.bitcoin-ii.org, or from bc2mempool.com if that host does not answer. That request shows the explorer your IP address. We do not store it.
How BitcoinII launched
BitcoinII is a new chain. In the whitepaper’s words it is “not a fork of the Bitcoin chain, not a sidechain, and not a derivative token.” Holding BTC does not give you BC2. The rules create coins only as a block subsidy: 50 BC2 until block 210,000, then half, up to a cap of 21,000,000. There is no premine in the rules. The genesis coinbase, 50 BC2, is unspendable.
The genesis block is 12 December 2024, 15:57 UTC. Its coinbase text is “BBC News 12/04/2024 French government collapses in no-confidence vote.”
Test mining began on 22 June 2025, with block 1. Open public mining began with the BitcoinTalk announcement on 2 July 2025.
Verify it yourself
Check the early blocks and the supply on a node you run, or on an explorer. Keep RPC on your own computer. Why that port stays private.
- Block 0 and block 1 on the explorer. The other explorers are on the network page.
- On your node, take the hash from
getblockhashand pass it togetblock:
bitcoinII-cli getblockhash 0
bitcoinII-cli getblock HASH
bitcoinII-cli getblockhash 1
bitcoinII-cli getblock HASH
bitcoinII-cli gettxoutsetinfo
gettxoutsetinfo reports the spendable coins your node can see. The words we use are in the glossary.
Why difficulty started at 1
A new chain starting at Bitcoin’s current difficulty could not attract enough hashrate to be secure. Starting at difficulty 1, as Bitcoin did in 2009, lets security grow with the network’s real hashrate.
ShockWave difficulty adjustment
ShockWave is a per-block difficulty adjustment. It shipped in BitcoinII Core v31.1.0 and has been active since block 57,750, mined Aug 29, 2026 (UTC). It uses a 25-block rolling baseline derived from Dark Gravity Wave v3, allows at most a 4× change in difficulty per block, and includes an emergency recovery mode for when blocks stall. It targets about 10 minutes per block.
Why it was needed
Under the original 2,016-block retarget, a burst of hashrate could leave the difficulty set for miners who had already gone. Confirmations then waited on long gaps. ShockWave adjusts the difficulty every block instead.
ShockWave’s source is published on GitHub for review under its own proprietary source-review license; it is not covered by the MIT license that applies to most of BitcoinII Core. The whitepaper predates ShockWave, so its description of a 2,016-block retarget is historical.
Money, not data
The whitepaper rejects the expansion of OP_RETURN data limits adopted in Bitcoin Core v30, and commits BitcoinII to “Bitcoin’s original purpose as a borderless, censorship resistant, inflation proof, responsible monetary system”. Since block 57,750, consensus rules limit arbitrary data in transactions:
- At most one OP_RETURN output per transaction, up to 83 bytes.
- No Ordinals inscription envelopes, and no OP_13 Runes marker in OP_RETURN.
- No bare multisig outputs and no Taproot annex.
- Taproot script-path scripts are capped at 3,600 bytes.
These rules limit arbitrary data; they do not make it impossible to put any data on chain.
Our view is that keeping large arbitrary data off the chain helps decentralization, because an ordinary computer can store and check the chain. The rule above is the mechanism: from block 57,750, one OP_RETURN output and at most 83 bytes. For context, the Bitcoin Core 30.0 release notes raise the default data-carrier size to 100,000 bytes and allow more than one OP_RETURN output in a transaction. The explorer publishes a size on each block. On 12 November 2026, block 63,780 was 334 bytes. That figure is one block, not the chain.
Other differences from Bitcoin
- Replay protection from block 57,750, so BC2 transactions can’t be replayed on another chain.
- Fork-aware header sync.
- Its own network: P2P port 8338, its own data folder and its own process.
A complement to Bitcoin
“BitcoinII does not ask users to abandon Bitcoin.” The whitepaper describes it as “not competition to Bitcoin, but complement: a second option, based on the same protocol”. Both can run on the same computer, with separate data folders, ports and processes. The project’s developers call it a sister chain.