Validators
What a Vordium validator does, what it needs, how the set is chosen, and how to join.
A validator runs VordiumBFT and VordCore: it votes on every batch, leads the heights it is given, and applies every batch to its own copy of the state. Validators also supply oracle prices and sign the bridge's payouts.
The set
The validator set is read from the chain (GET /registry/set) for the selected network:
| Right now | |
|---|---|
| Seats | — |
| Seated validators | — |
| Seats Vordium keeps | — |
| Largest share of voting power | — |
| Smallest bond | — |
| Epoch | — |
Validators are shown by address only:
—
What it takes
- Hardware: 8 vCPU and 32 GB of memory, with fast storage and a steady connection.
- Two keys: a cold operator key that never touches the node, and a validator hot key generated on the node, which holds no funds and cannot move a bond.
- The public node files: github.com/Vordium/node — releases, signatures, the visor, configuration templates and the operator tools.
Penalties
Vordium never takes a validator's stake. There is no slashing — not for downtime, not for double-signing, not at any rate. A validator that misbehaves or goes offline is jailed: it stops earning until it is unjailed.
Network facts last checked against the network 2026-10-22 13:00:37 UTC · mainnet spec v28 · testnet spec v8