Running a Validator
Validators are responsible for committing new blocks to the blockchain through voting. A validator's stake is slashed if they become unavailable or sign blocks at the same height. Please read about Sentry Node Architecture to learn how to protect your node from DDOS attacks and to ensure high-availability on mainnet.
- CPU - 4/8 Core
- Memory - 8/16GB
- Disk - SSD or NVMe
- Size - 512GB or larger
- 100 (current) which was extended from 85 recently
- Tokens to stake to be active = more than last active validator
- Check with the command
$votingpowerin the Akash Discord server's > validators-status channel for current requirements to get into the active validator set
- You can stake by yourself or from external wallets within your community
Prior to validator creation we must create an Akash account for validator use. Use the steps covered in this guide to create this account. NOTE - only the `Create an Account` and `Fund your Account` sections of this guide need to be completed for this purpose.
Configure settings to communicate with the Akash blockchain as follows:
export AKASH_CHAIN_ID="$(curl -s "$AKASH_NET/chain-id.txt")"
akashvalconspubcan be used to create a new validator by staking tokens. You can find your validator pubkey by running:
akash tendermint show-validator
The file that stores this private key lives at
~/.akash/config/priv_validator_key.json. To create your validator, just use the following command.
Note that in the output of this command your `akashvaloper` address will be revealed. Note this address for future use including the verification steps later in this guide.
akash tx staking create-validator \
--pubkey="$(akash tendermint show-validator)" \
::: tip When specifying commission parameters, the
commission-max-change-rateis 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-delegationis a stritly positive integer that represents the minimum amount of self-delegated voting power your validator must always have. A
min-self-delegationof 1 means your validator will never have a self-delegation lower than
You can confirm that you are in the validator set by using a third party explorer for the testnet you are joining.
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 (
--monikerdefaults to the machine name) if the field has never been set or remain the same if it has been set in the past.
$AKASH_KEY_NAMEspecifies the key for the validator which you are editing. If you choose to not include certain flags, remember that the
--fromflag must be included to identify the validator to update.
--identitycan be used as to verify identity with systems like Keybase or UPort. When using with Keybase
--identityshould be populated with a 16-digit string that is generated with a keybase.io account. It's a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows explorers to retrieve your Keybase avatar. This is how you can add a logo to your validator profile.
akash tx staking edit-validator
--details="The SUPERCLOUD IS HERE!" \
commission-ratevalue must adhere to the following invariants:
- 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 changeits commission once per day and within
View the validator's information with this command:
akash query staking validator $AKASH_VALIDATOR_ADDRESS
In order to keep track of a validator's signatures in the past you can do so by using the
akash query slashing signing-info $AKASH_VALIDATOR_PUBKEY \
When a validator is "jailed" for downtime, you must submit an
Unjailtransaction from the operator account in order to be able to get block proposer rewards again (depends on the zone fee distribution).
akash tx slashing unjail \
- Ensure that the field `catching_up` is false and that the latest block corresponds to the current block of the blockchain
akash query staking validator <akashvaloper-address>
akash query staking validator akashvaloper16j3ge9lkpgtdkzntlja08gt6l63fql60xdupxq
- Status will display as `BOND_STATUS_UNBONDED` after initial build
Your validator is active if the following command returns anything
NOTE - this command will only display output of your validator is in the active set
akash query tendermint-validator-set | grep "$(akash tendermint show-validator)"
You should now see your validator in one of the Akash Testnet explorers. You are looking for the
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-heightto the height at which you want your node to shutdown or by passing the
akash. The node will shutdown with a zero exit code at that given height after committing the block.
Your validator has become jailed. Validators get jailed, i.e. get removed from the active validator set, if they do not vote on
500of the last
10000blocks, or if they double sign.
If you got jailed for downtime, you can get your voting power back to your validator. First, if
akashis not running, start it up again. If you are running
systemdthis will be different:
Lastly, 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!
The default number of files Linux can open (per-process) is
akashis known to open more than
1024files. This causes the process to crash. A quick fix is to run
ulimit -n 4096(increase the number of open files allowed) and then restart the process with
akash start. If you are using
systemdor another process manager to launch
akashthis may require some configuration at that level. See the
systemdconfiguration doc for details on how to configure
systemdto aleviate this issue.