Becoming a Validator
An Orbinum validator runs a node, bonds ORB of its own and stands as a candidate. Once per era the chain elects the active set from the candidates and the stake behind them; the elected validators author and finalize blocks and share the era's rewards with the nominators who backed them.
What a validator does
Authors blocks. Aura assigns slots round-robin among the active set. Your node builds a block when its slot comes up, every 6 seconds, and earns 20 era points for it.
Finalizes blocks. GRANDPA votes on chains rather than individual blocks. A block is final once more than two thirds of the set has voted for a chain containing it — roughly 12 seconds.
Includes private transactions. unshield and private_transfer arrive as unsigned
extrinsics with the fee sealed inside the ZK proof. Each one's fee is credited to the
validator that authored the block — see Spend fees.
What a validator is
| Identity | What it is | Where it comes from |
|---|---|---|
| Validator account (SS58) | Your staking account: it bonds, validates, and is paid | Talisman or SubWallet (or any Substrate signer) |
| Session keys | Aura (sr25519) to author, GRANDPA (ed25519) to finalize | Generated on the node, registered with session.setKeys from the validator account |
| Peer ID | The node's libp2p identity | Derived from the node key (VALIDATOR_NODE_KEY) |
Blocks are attributed to the account behind the session keys that sealed them.
Requirements to stand
| Requirement | Testnet | Mainnet |
|---|---|---|
| Self-bond | at least 1,000 ORB | at least 100,000 ORB (indicative, not yet defined) |
| Session keys | registered with session.setKeys | same |
| Admission | on the allowlist (permissioned) | as governance sets it |
| Node | synced, on a current release, with telemetry on | same |
On the testnet admission is permissioned: governance keeps an allowlist of
operators (validatorSet.approvedValidators), and only accounts on it can stand.
Governance can open admission to any account; the minimum self-bond then rises to
100,000 ORB. See How staking works.
The steps
- Provision the server — dedicated CPU, an open P2P port, and an account with enough ORB for the bond and fees.
- Run the node and generate session keys —
Docker Compose, sync, then
author_rotateKeysWithOwner. - Bond, register keys and validate — in the app's Staking → Validator page, or with extrinsics.
- Wait for the election. Your candidacy counts at the next election, about two hours before the era ends; if elected, you take over at the next era.
- Operate — watch health, nominators and rewards; change commission; rotate keys; stop.
Earnings and risk
| Source | How it is paid |
|---|---|
| Era rewards | The era's new issuance on the yearly schedule plus the era's transaction fees, split by era points. You take your commission, the rest is shared with your nominators by stake. Paid automatically — see Rewards |
| Tips | Substrate tips and EVM priority fees of the blocks you author, straight to your account |
| Spend fees | Fees of private transactions in your blocks, claimed from the pool — see below |
Risk. Signing two conflicting finality votes — usually by running the same session keys on two nodes — slashes your own bond (not your nominators'), bans you and disables your node. Downtime is not slashed, but earns no points. See Slashing.
Spend fees
Every private_transfer and unshield carries a fee (at least 0.001 ORB). It is
credited to the block author's account as a pending balance inside the shielded pool,
and you claim it.
The simplest way is the app: connect your validator account and open Staking → Validator → Rewards, or Wallet → Public. The Validator fees panel shows what is pending; Claim pays it to that account.
From Polkadot.js Apps instead: each credited fee emits
shieldedPool.FeeCredited { validator, asset_id, amount }. Your running total is in
Developer → Chain state → shieldedPool.pendingFees(yourAccount, 0) (asset 0 is
ORB). To collect it, in Developer → Extrinsics, sign with your validator account:
shieldedPool.claimFees(assetId = 0, amount)
amountcan be any part of the pending balance; the rest stays pending.- The funds land in the same account's public balance and the call emits
FeesClaimed. Shield the proceeds afterwards if you want them private. - Pending fees never expire, and leaving the set does not clear them.
- A fee paid in a private pool's shares (
sN, for example by a private exit) is redeemed for you as it is paid: its value unbonds from the pool and reaches your account as ORB after 2 eras (privateStaking.FeesRedeemed). It only waits in your pending fees if it cannot be redeemed at once.
The full mechanism is in Spend Fees.
Timing
| Parameter | Value |
|---|---|
| Block time | 6 seconds |
| Session | 600 blocks ≈ 1 hour |
| Era | 24 sessions ≈ 1 day |
| Election | about 2 hours before the era ends |
| Validator unbonding | 28 eras ≈ 28 days |
Related
- Staking — every role and how they fit
- How staking works — admission and the election
- Consensus — Aura and GRANDPA