$votingpowerin the Akash Discord server's > validators-status channel for current requirements to get into the active validator set
akashvalconspubcan be used to create a new validator by staking tokens. You can find your validator pubkey by running:
~/.akash/config/priv_validator_key.json. To create your validator, just use the following command:
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
--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.
commission-ratevalue must adhere to the following invariants:
commission-max-change-ratewhich is maximum
Unjailtransaction from the operator account in order to be able to get block proposer rewards again (depends on the zone fee distribution).
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.
500of the last
10000blocks, or if they double sign.
akashis not running, start it up again. If you are running
systemdthis will be different:
akashcrashes because of
too many open files
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.