Become a Validator
Prerequisites
225K NOM to use for the minimum required self-delegation. Consider a buffer in case of unforeseen slashing.
Create a Validator
STEP 1: Create or add keys for the validator. Be sure to secure the mnemonic from the output.
You may also recover keys from a mnemonic:
Be sure the validator account is funded with the minimum self-delegation of 225K NOM.
STEP 2: Verify balances with the following:
STEP 3: Register your validator node:
anom is the smallest denomination of NOM. The minimum required 225,000 NOM self-delegation amount is written as 225000000000000000000000anom. This contains 18 zeros after 225,000. Update with the correct value you are self-delegating, as well as the other variables. Descriptions:
amount
: Amount of aNOMs to self delegate. 1 NOM = 10^18 aNOMpubkey
: By using the command onomydtendermint show-validator
, the private key will be provided in .onomyd/config/priv_validator_key.json as your validator's signing key. Make sure to backup this file.moniker
: Name of the validatorwebsite
(optional) : Website of the organization/individual running validatoridentity
(optional) : Pgp key generated using UPort or KeyBasecommission-rate
: Commission rate of the validatorcommission-max-rate
: Maximum commission a validator can chargecommission-max-change-rate
: Maximum daily increase of a validator commissionmin-self-delegation
: Minimum NOM a validator must keep bonded - this cannot be lower 225,000 NOM. The minimum amount of self delegation for your validator to be active. If you withdraw your self delegation to below this threshold, your validator will be immediately removed from the active set. Your validator will not be slashed, but will stop earning staking rewards.
STEP 4: Check if your validator is operational:
You have succeeded if the status is BOND_STATUS_BONDED
Welcome to the Onomy Validator Guild!
Migrating servers
When validators are moved ensure that you copy the priv_validator_key.json
file into the new node config folder. The mnemonic is not enough. You must copy over priv_validator_key.json
The steps are as follows:
sync node B as a completely new and fresh node
stop node B once complete
stop original node A
delete
priv_validator_keys.json
on node A (make sure to backup this file or copy its contents into a new local file before deleting)restart node A
check with
onomyd status
that the voting power of node A is 0import
priv_validator_keys.json
on node Bstart node B
confirm voting power is now on node B with
onomyd status
Last updated