Technical reference

Chain identity and integration data

A dated fact sheet for node operators, miners, wallet developers, researchers, exchanges, and custodians. Unknown fields remain explicit.

Chain comparison

Three related states, distinct operational rules

Bitcoin BTC mainnet, the historical SHA-256d enforcement branch, and the intended Bitcoin BIP110 continuation share lineage but require separate identity checks.

PropertyBitcoin BTC mainnetHistorical enforcement branchBitcoin BIP110
Shared historyThrough 961,631Through 961,631Inherits shared history and enforcement-branch blocks
First divergent height961,632961,632961,632; later BLAKE2b height pending
Proof of workSHA-256dSHA-256dBLAKE2b after confirmed activation
Header formatBitcoin 80-byte headerBitcoin 80-byte headerBLAKE2b 164-byte header v2 in current development
Mining hardwareSHA-256d Bitcoin ASICsSHA-256d Bitcoin ASICsSpecifically tested BLAKE2b hardware and firmware
Reduced-data rulesNot activated through BIP 110Original deployment never reached ACTIVEActive with BLAKE2b in RC2 testnet code; mainnet pending
DifficultyBitcoin mainnet rulesOriginal inherited rulesReset, adjustment, and boundary must be fixed in mainnet source
Replay behaviorAccepts ordinary Bitcoin transactionsOrdinary transactions remain mutually replayableOpt-in SIGHASH_UNIFIED on RC2 testnet; mainnet pending
Reference softwareMultiple Bitcoin implementationsExact enforcing release and commit requiredFork-specific signed release, tag, and commit required
Asset identityBTCHistorical branch stateBitcoin BIP110; project-declared ticker BIP110
Snapshot statusActive networkSHA-256d tip 961,638 observed 24 Aug 2026BLAKE2b testnet active; BLAKE2b mainnet inactive

Exchange and custody integration

Fact sheet

Integration should begin after maintainers publish reproducible software and stable network parameters. The block-hash identity check is essential because the current RPC chain name, network magic, port, and address formats overlap Bitcoin mainnet.

Exchange display name
Bitcoin BIP110 (project declaration)
Exchange ticker
BIP110 (project declaration; services may choose another identifier)
Asset type
Native coin
Consensus
Proof of work
Proof of work at observed branch tip
SHA-256d at height 961,638, observed 24 August 2026
Planned proof of work
BLAKE2b header v2; final mainnet parameters pending
Origin chain
Bitcoin
Last common height
961,631
Last common block hash
00000000000000000000807f9dc917442a67910426d79ebb2f8aa2149327ce8a
First divergent height
961,632
First Bitcoin BIP110 block hash
0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16
First BLAKE2b mainnet height
Unavailable. A mainnet activation height has not been published.
First BLAKE2b mainnet hash
Unavailable. No BLAKE2b mainnet block has been mined.
Genesis block hash
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
RPC network name
main (not a unique Bitcoin BIP110 chain identifier)
Required RPC identity check
getblockhash 961632 must return 0000000000000000000169eb6f811ddbd0daf343af7b62180cdb13e7c78dbc16
P2P network magic
f9 be b4 d9 in current development source; identical to Bitcoin mainnet and subject to change
Default P2P port
8333 in current development source; identical to Bitcoin mainnet and subject to change
Address formats
P2PKH 1... (0x00); P2SH 3... (0x05); SegWit bc1q...; Taproot bc1p...
Decimal places
8
Subsidy and halving
Initial subsidy 50 BIP110; halves every 210,000 blocks; 3.125 BIP110 at height 961,638; next halving at 1,050,000
Coinbase maturity
100 blocks
Replay protection
None active on the observed SHA-256d branch; opt-in SIGHASH_UNIFIED implemented on RC2 testnet; mainnet pending
Reference node status
No stable Bitcoin BIP110 mainnet release published
Testnet reference candidate
Bitcoin Knots 29.4.1 / Knots 20260508rc2; tag v29.4.1.knots20260508rc2
RC2 commit
c25ad6bcd18fa65cd78f176a52be062411507741
Mainnet release hashes and signatures
Unavailable because no stable mainnet artifacts have been published
Website
bitcoinbip110.org
Technical contact
Not yet published
Security contact
Not yet published
Machine-readable network snapshot

JSON fields match this dated reference and retain pending values as explicit nulls.

Download JSON

Activation checklist

Evidence required for mainnet readiness

A mainnet announcement should be matched to signed, reproducible source and independent node observations. Testnet parameters do not substitute for a mainnet specification.

  • Signed stable release tag and exact commit
  • Reproducible binaries, hashes, and signatures
  • Mainnet activation height and parent block hash
  • BLAKE2b target shift and adjustment algorithm
  • Exact header-v2 serialization and test vectors
  • RDTS activation and expiry composition
  • Required first-block coinbase commitment
  • Replay-protection activation and wallet behavior
  • P2P identity, seeds, ports, and network magic
  • Independent observation of the first valid block
  • Miner and firmware compatibility evidence
  • Explorer and wallet chain-identity verification