Register a Validator

This is a detailed step-by-step guide for setting up a XPLA Chain validator. Please be aware that while it is easy to set up a rudimentary validating node, running a production-quality validator node with a robust architecture and security features requires an extensive setup.

For more information on setting up a validator, see additional resources.

Prerequisites #

• You have completed how to run a full node, which outlines how to install, connect, and configure a node.
• You are familiar with xplad.
• You have read through the validator FAQ
• You understand the different keys of a validator in the FAQ

1. Retrieve Your PubKey #

The Consensus PubKey of your node is required to create a new validator. Run:

--pubkey=$(xplad tendermint show-validator)

2. Create a New Validator #

To create the validator and initialize it with a self-delegation, run the following command. key-name is the name of the Application Operator Key that is used to sign transactions.

xplad tx staking create-validator \
    --amount=5000000000000000000axpla \
    --pubkey=$(<your-consensus-PubKey>) \
    --moniker="<your-moniker>" \
    --chain-id=<chain_id> \
    --from=<key-name> \
    --commission-rate="0.10" \
    --commission-max-rate="0.20" \
    --commission-max-change-rate="0.01" \
    --min-self-delegation="1"

3. Confirm Your Validator is Active #

If running the following command returns something, your validator is active:

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

You are looking for the bech32 encoded address in the ~/.xpla/config/priv_validator.json file.

4. Secure Your Keys and Have a Backup Plan #

Protecting and having a contingency backup plan for your keys will help mitigate catastrophic hardware or software failures of the node. It is a good practice to test your backup plan on a testnet node in case of node failure.