3 · Download & verify — Vordium Docs

On approval the operator sends you a one-time, 24-hour link for the node binary and the genesis file — the binary is never public. Verify the binary's sha256 against the value the operator gives you on approval: the admin panel surfaces the published binary_sha256 the moment they issue your link (it is also returned alongside the link). Verify the genesis the same way against the published genesis_sha256 — a whole-file sha256 of the exact genesis the live validators booted. The genesis is boot-stamped (two wipe-time clock fields: vord_emission_t0_ms and bridge_start_arb_block), so this value is republished at every relaunch; the current value is 29875e24d563679aac93249a251090a17b2819bf86ece6024816bfaf350b8429. Do not boot until both hashes match — a genesis mismatch means a divergent state root and a failed sync. (Note: internal relaunch runbooks also carry a source-manifest fingerprint of the pre-stamp template; that is a core-operator cross-check, not the genesis download hash — always verify the genesis_sha256 above.)

Bash

curl -sL "https://vordscan.io/api/validators/download/binary?token=<token>"  -o vordiumchain
curl -sL "https://vordscan.io/api/validators/download/genesis?token=<token>" -o vordium-genesis-v6.json
sha256sum vordiumchain             # must equal the published binary_sha256
sha256sum vordium-genesis-v6.json  # must equal the published genesis_sha256 (whole-file sha256)
curl -sL "https://vordscan.io/api/validators/download/boot-bundle?token=<token>" -o boot-bundle.tar.gz
sha256sum boot-bundle.tar.gz       # must equal the published boot_bundle_sha256 (verify BEFORE extract)