Run a node

The full operator guide for each network is in the public node repository: mainnet and testnet. This page is the outline.

The one rule

A validator runs nothing it has not verified against the pinned release key. The vordium-visor starts the node and checks, at every start, that the node binary's hash is in the signed manifest, that the manifest is signed by the pinned release key and no other, that the genesis file matches its published hash, and that the key file carries the pinned fingerprint. Never run the node binary directly.

Release key fingerprint:

C5EB 4728 F660 369C E519 D834 B48F B4B7 1EFD 48AE

Release channels

Each channel serves a signed releases.json (read current), the binaries, SHA256SUMS.<release> with its signature, and genesis.sha256.

Steps

1. Download and verify the current release: the key, then the signatures, then the files.
2. Check the genesis: sha256sum of the genesis file must equal genesis.sha256, and a live node reports the same value in GET /status (genesis_sha256). On the main network the genesis file is given to admitted validators.
3. Generate the hot key on the box — never copy one in.
4. Configure from the templates: only paths, keys and pruning are yours to edit; consensus values are the same on every validator. Peers are given to you when you are accepted.
5. Print your join request with --join-request — public values only: address, hot key, VRF key, name.
6. Start the signer and the node through the visor.

On the testnet the visor also updates the node to each new signed release by itself.