Become a Validator
Last updated
Last updated
225K NOM to use for the minimum required self-delegation. Consider a buffer in case of unforeseen slashing.
STEP 1: Create or add keys for the validator. Be sure to secure the mnemonic from the output.
onomyd keys add validator
You may also recover keys from a mnemonic:
onomyd keys add --recover validator
Be sure the validator account is funded with the minimum self-delegation of 225K NOM.
STEP 2: Verify balances with the following:
onomyd q bank balances <account address starting with onomy1>
STEP 3: Register your validator node:
onomyd tx staking create-validator \
--pubkey $(onomyd tendermint show-validator) \
--moniker "the name of your validator" \
--details "a description of your validator" \
--identity "your keybase.io PGP key (your pfp will be used in apps)" \ # optional
--website "http://homepage.validator.com" \ # optional
--security-contact "contact@your.email" \ # optional
--min-self-delegation 225000000000000000000000 \
--commission-rate "0.05" \
--commission-max-rate "0.20" \
--commission-max-change-rate "0.01" \
--amount 225000000000000000000000anom \
--from validator \
--chain-id onomy-mainnet-1 \
--gas auto \
--gas-adjustment 1.4 \
--gas-prices 0anom
STEP 4: Check if your validator is operational:
onomyd query staking validator $(onomyd keys show validator --bech val --address) --output json | jq
You have succeeded if the status is BOND_STATUS_BONDED
Welcome to the Onomy Validator Guild!
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 0
import priv_validator_keys.json
on node B
start node B
confirm voting power is now on node B with onomyd status