BLACKCOIN / PROTOCOL V4IDENTITY

CHAIN IDENTITY / VERSIONED & VERIFIABLE

Blackcoin chain identity

The manifest preserves its signed v30.1.3 identity baseline; this is source provenance, not a recommendation to install that historical version. Current software is listed in the published release catalog with 30.1.5.1 guidance. The genesis hash and Merkle root were verified from block 0 through the public explorer before publication. The machine-readable copy lives in /api/chain-params (schema blackcoin.chain-params/3) and never mutates silently.

Identity manifest

  • Genesis hash: 000001faef25dec4fbcf906e6242621df2c183bf232f263d0ba5b101911e4563
  • Genesis Merkle root: 12630d16a97f24b287c8c2594dda5fb98c9e6c70fc61d44191931ea2aa08dc90
  • Network message start: 70352205
  • Base58 prefixes: pubkey 25 (B…) · script 85 · secret key 153
  • bech32 HRP: blk
  • BIP44 coin type: 10
  • Quantum replay domain: 424c4b00
  • Decimals: 8 (1 BLK = 100,000,000 sats)
  • Historical identity reference: 86c6855ab135afe784635a564f21c74d67aa366b (v30.1.3; not the current-release selector)

Shared history and scheduled rules

  1. Inherited history, scheduled rules. This implementation builds on Blackcoin history from genesis and adds the Protocol V4 accounting overlay. Scheduled rules apply at their activation heights. Shared ancestry does not establish that every implementation accepts the same later tip; compare exact hashes and rule sets.
  2. First scheduled differing rule. The competing-claim activation boundary is height 5,993,200; the migration boundary follows at height 6,193,000. Activation at or above a scheduled height is not proof of a branch split; compare exact hashes and rule sets. Heights control; dates are projections.
  3. Future branch anchors stay null. The hashes of block 6,192,999 (Gold Rush final) and block 6,193,000 (Migration start) are published as null in the manifest until those blocks exist and are independently finalized. Their hashes are not predicted.
  4. "Canonical anchor" defined narrowly. On this site it means the observer-accepted deployment view at the stated time and source. The term is a technical designation; it does not establish legal, social, or universal authority. This is an independently maintained implementation; verify everything against your own node via the reproduction contract.