NOTE: it is not required to create a validator on Akash testnets unless specified in a challenge or otherwise. The akash team runs a centralized validator set to enable for easy and consistent testnet operations for developers trying out the platform for the first time.
akashvalconspub can 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-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 min-self-delegation of 1 means your validator will never have a self-delegation lower than 1000000uakt :::--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.$AKASH_KEY_NAME specifies the key for the validator which you are editing. If you choose to not include certain flags, 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 with Keybase --identity should 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-rate value must adhere to the following invariants:commission-max-ratecommission-max-change-rate which is maximumcommission-max-change-rate bounds.signing-info command:Unjail transaction from the operator account in order to be able to get block proposer rewards again (depends on the zone fee distribution).bech32 encoded address in the ~/.akash/config/priv_validator.json file.halt-height to the height at which you want your node to shutdown or by passing the --halt-height flag to akash. The node will shutdown with a zero exit code at that given height after committing the block.voting_power: 0500 of the last 10000 blocks, or if they double sign.akash is not running, start it up again. If you are running systemd this will be different:akash crashes because of too many open files1024. akash 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 restart the process with akash start. If you are using systemd or another process manager to launch akash this may require some configuration at that level. See the systemd configuration doc for details on how to configure systemd to aleviate this issue.