# Running a Validator
We suggest you try out joining a public testnet first. Information on how to join the most recent testnet can be found here.
Before setting up a validator node, make sure to have completed the Joining Mainnet guide.
If you plan to use a KMS (key management system), you should go through these steps first: Using a KMS.
# What is a Validator?
Validators are responsible for committing new blocks to the blockchain through an automated voting process. A validator's stake is slashed if they become unavailable or sign blocks at the same height. Because there is a chance of slashing, we suggest you read about Sentry Node Architecture to protect your node from DDOS attacks and to ensure high-availability.
If you want to become a validator for the Hub's
mainnet, you should learn more about security.
The following instructions assume you have already set up a full-node and are synchonised to the latest blockheight.
# Create Your Validator
cosmosvalconspub can be used to create a new validator by staking tokens. You can find your validator pubkey by running:
To create your validator, just use the following command:
Don't use more
uatom than you have!
When specifying commission parameters, the
commission-max-change-rate is used to measure % point change over the
commission-rate. E.g. 1% to 2% is a 100% rate increase, but only 1 percentage point.
Min-self-delegation is a stritly positive integer that represents the minimum amount of self-delegated voting power your validator must always have. A
1000000 means your validator will never have a self-delegation lower than
It's possible that you won't have enough ATOM to be part of the active set of validators in the beginning. Users are able to delegate to inactive validators (those outside of the active set) using the Keplr web app (opens new window). You can confirm that you are in the validator set by using a third party explorer like Mintscan (opens new window).
# Edit Validator Description
You can edit your validator's public description. This info is to identify your validator, and will be relied on by delegators to decide which validators to stake to. Make sure to provide input for every flag below. If a flag is not included in the command the field will default to empty (
--moniker defaults to the machine name) if the field has never been set or remain the same if it has been set in the past.
The <key_name> specifies which validator you are editing. If you choose to not include some of the flags below, remember that the --from flag must be included to identify the validator to update.
--identity can be used as to verify identity with systems like Keybase or UPort. When using Keybase,
--identity should be populated with a 16-digit string that is generated with a keybase.io (opens new window) account. It's a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile.
Please note that some parameters such as
commission-max-change-rate cannot be changed once your validator is up and running.
commission-rate value must adhere to the following rules:
- Must be between 0 and the validator's
- Must not exceed the validator's
commission-max-change-ratewhich is maximum % point change rate per day. In other words, a validator can only change its commission once per day and within
# View Validator Description
View the validator's information with this command:
# Track Validator Signing Information
In order to keep track of a validator's signatures in the past you can do so by using the
# Unjail Validator
When a validator is "jailed" for downtime, you must submit an
Unjail transaction from the operator account in order to be able to get block proposer rewards again (depends on the zone fee distribution).
# Confirm Your Validator is Running
Your validator is active if the following command returns anything:
You should now see your validator in one of the Cosmos Hub explorers. You are looking for the
address in the
# Halting Your Validator
When attempting to perform routine maintenance or planning for an upcoming coordinated upgrade, it can be useful to have your validator systematically and gracefully halt. You can achieve this by either setting the
halt-height to the height at which you want your node to shutdown or by passing the
--halt-height flag to
gaiad. The node will shutdown with a zero exit code at that given height after committing
# Advanced configuration
You can find more advanced information about running a node or a validator on the Tendermint Core documentation (opens new window).
# Common Problems
# Problem #1: My validator has
Your validator has become jailed. Validators get jailed, i.e. get removed from the active validator set, if they do not vote on at least
500 of the last
10,000 blocks, or if they double sign.
If you got jailed for downtime, you can get your voting power back to your validator. First, if you're not using Cosmovisor (opens new window) and
gaiad is not running, start it up again:
Wait for your full node to catch up to the latest block. Then, you can unjail your validator
After you have submitted the unjail transaction, check your validator again to see if your voting power is back.
You may notice that your voting power is less than it used to be. That's because you got slashed for downtime!
# Problem #2: My
gaiad crashes because of
too many open files
The default number of files Linux can open (per-process) is
gaiad is known to open more than
1024 files. This causes the process to crash. A quick fix is to run
ulimit -n 4096 (increase the number of open files allowed) and then restarting the process with
gaiad start. If you are using
systemd or another process manager to launch
gaiad (such as Cosmovisor (opens new window)) this may require some configuration at that level. A sample
systemd file to fix this issue is below: