Managing your Validator
This is your quick reference on how to manage your validator node.
Delegate Additional Furya to your Validator
You can always use the furyad CLI to send a delegation transaction.
Jailed!
If your validator goes offline and misses too many blocks, it will be removed from the active set & “jailed”. In this state, your delegations will be slowly slashed!! Check whether your validator is jailed using the furyad query staking validator
command.
If you still have enough delegations to enter the active set, simply run this command to unjail it:
Edit your Validator’s Info
From time to time you may want to rename your validator, change the description, etc. Do this by:
A flag is only needed if it is to be changed (e.g. if you do not wish to change the security contact email, then it doesn’t need to included in the command)
Withdraw Commissions
Run the following command to claim your commissions:
Note the --commission
flag.
Migrating Servers
To migrate your validator to a new server, you first sync up a new node (check the instruction on using snapshot or state sync). Then:
- Shut down your old node
- Copy your
priv_validator_key.json
andpriv_validator_state.json
to the new node - Restart your new node; you should see the “This node is a validator” log message when starting up
NOTE: Step (1) must be done first, or your validator may double-sign!!!
Optional: Copy node_key.json
to the new server as well. This is not mandatory, but helps your node to establish P2P connections faster.
Was this page helpful?