Validator Operations Guide

This document provides instructions for managing and monitoring your validator node throughout its operational lifecycle.

Inspecting Validator Details

Retrieve comprehensive information about your validator using the following command:

xosd query staking validator <account>

Monitoring Validator Performance

Examine a validator's historical signing record and performance metrics with the signing-info command:

xosd query slashing signing-info <validator-pubkey> --chain-id=<chain_id>

Restoring a Penalized Validator

If your validator has been temporarily suspended ("jailed") due to reliability issues, execute an Unjail transaction from the operator's account to regain block proposition eligibility and associated rewards:

xosd tx slashing unjail --from=<key_name> --chain-id=<chain_id>

Verifying Active Status

Confirm your validator's active participation in consensus with this verification command:

xosd query tendermint-validator-set | grep "$(xosd tendermint show-address)"

A non-empty response indicates active validator status. Your validator should also appear in XOS blockchain explorers. The validator can be identified using the bech32 encoded address found in the ~/.exprd/config/priv_validator.json file.

Note: Validator inclusion requires sufficient voting power to rank within the top 100 validators.

Controlled Shutdown Procedure

For scheduled maintenance or coordinated network upgrades, implement a controlled validator shutdown by specifying a termination block height. Set the halt-height parameter to your desired shutdown block, or use the --halt-height flag with the xosd command. This ensures your node will gracefully terminate with a clean exit code (0) after committing the specified block.