BLACKCOIN / PROTOCOL V4VERIFY

RELEASES / NODE CHECKS

Verify releases and reproduce chain records.

Run a verified published production release from the downloads rail on a compatible indexed node. After syncing, use the commands below to compare chain records at the same height and hash. Check source provenance, RPC support, and the data's quality/verification timestamp before comparing. The 30.1.5.1 guide explains that release's version identity and upgrade boundary. Verify exact source and package records before execution; a signed Git commit is not platform code signing.

The reproduction contract

  1. Anchor and tip. Run blackcoin-cli getblockchaininfo and compare blocks and bestblockhash with the anchor shown in the live ledger and in /api/v3/quantum.
  2. Shadow state. Run blackcoin-cli getgoldrushstate. The pools, counts, and target bits must equal the snapshot fields exactly. The schema-12 replay_state block, including its commitment hash, is the same attestation shown in the Authenticated Replay Integrity panel.
  3. UTXO commitment. Run blackcoin-cli gettxoutsetinfo muhash at an identical block hash and index state to compare commitments from independently operated nodes. A mismatch requires investigation; commitments from different tips are not directly comparable.
  4. Any block, transaction, or payout. getgoldrushblock <height>, getrawtransaction <txid> 2, getshadowtransaction <synthetic_txid>, getshadowaddress <address>. Each explorer record cites the exact identifiers to feed these calls.
  5. Supply. gettxoutsetinfo muhash reports total_amount, the same base-chain figure served at /api/supply. Synthetic Gold Rush credits are phase-locked and excluded until Migration; getshadowsupply reproduces that ledger.
  6. The release itself. Verify SHA256SUMS.txt, the SSH-signed source commit and tag, the SPDX SBOM, and the build-provenance attestation from the release record before running anything.

If results disagree after matching the exact block hash, source rules, and index coverage, file a sanitized report on the issue tracker ↗ with both outputs. During an interruption, eligible dashboard aggregates may retain explicitly labeled last-verified data for up to one hour; that label never means the data is current. Transaction, address, UTXO, search, and readiness endpoints remain strict.