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 current release and upgrade guide explains release selection, backups, and upgrade checks.
Verify a downloaded package · Compare chain data with your node
Verify a downloaded package
- Open the exact release record. Select your release in the published catalog. Check the tag and the linked
Blackcoin-Dev/BlackcoinGitHub record. Download the package for your operating system and architecture, plusSHA256SUMS.txtfrom that same release. Keep the original filenames. - Find the expected digest. Open
SHA256SUMS.txtas text and locate the line for the exact package filename. Its SHA-256 digest must contain 64 hexadecimal characters. A checksum for a different package or release does not verify your file. - Compute the file's digest. Open a terminal in the download folder. Use the command for your system below, replacing
PACKAGE_FILENAMEwith the downloaded package's exact filename. Quotation marks keep filenames containing spaces together. These commands read the package without running it.
Windows PowerShell
Get-FileHash -Algorithm SHA256 -LiteralPath '.\PACKAGE_FILENAME' | Select-Object -ExpandProperty HashmacOS Terminal
shasum -a 256 "./PACKAGE_FILENAME"Linux terminal
sha256sum "./PACKAGE_FILENAME"Compare all 64 characters. The computed digest must match the digest for that filename in SHA256SUMS.txt; letter case does not matter. On macOS and Linux, compare the digest before the filename in the command output. A missing file, command error, missing manifest entry, or mismatch means verification has not passed. Do not launch the package; check the filename and exact release record, then obtain a fresh copy if needed.
Check authenticity separately
A matching checksum establishes that the package matches the manifest you obtained. Establishing the publisher's identity also requires a trusted source for that manifest and the release's source-signature and provenance evidence. Follow the exact release's published verification instructions for SOURCE_COMMIT.txt, the SSH-signed commit and tag, build provenance, and SPDX SBOM. Confirm the expected signing key through a trusted project source before trusting a signature. This page does not supply a signing key or treat a checksum match as a signature check.
Windows packages lack Authenticode signatures. macOS apps use ad-hoc signatures and are not Developer ID signed or notarized. A signed Git source object does not establish platform code signing or an independent security audit. Review the release's platform notices before launch. If the identity or verification evidence is unclear, use the project support channels before proceeding.
Reproduce chain data with your node
- Anchor and tip. Run
blackcoin-cli getblockchaininfoand compareblocksandbestblockhashwith the anchor shown in the live ledger and in/api/v3/quantum. - Shadow state. Run
blackcoin-cli getgoldrushstate. The pools, counts, and target bits must equal the snapshot fields exactly. The schema-12replay_stateblock, including itscommitmenthash, is the same attestation shown in the Authenticated Replay Integrity panel. - UTXO commitment. Run
blackcoin-cli gettxoutsetinfo muhashat 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. - 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. - Supply.
gettxoutsetinfo muhashreportstotal_amount, the same base-chain figure served at/api/supply. Synthetic Gold Rush credits are phase-locked and excluded until Migration;getshadowsupplyreproduces that ledger. - 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.