#KEYBASE API CODE#

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. # Common Problems # Problem #1: My validator has voting_power: 0 You can find more advanced information about running a node or a validator on the Tendermint Core documentation (opens new window).

#KEYBASE API CODE#

The node will shutdown with a zero exit code at that given height after committing 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. 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 are looking for the bech32 encoded address in the ~/.gaia/config/priv_validator.json file. You should now see your validator in one of the Cosmos Hub explorers. Gaiad query tendermint-validator-set | grep ' $(gaiad tendermint show-address )' Your validator is active if the following command returns anything: chain-id = # Confirm Your Validator is Running 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). In order to keep track of a validator's signatures in the past you can do so by using the signing-info command: Gaiad query staking validator # Track Validator Signing Information View the validator's information with this command: Its commission once per day and within commission-max-change-rate bounds. In other words, a validator can only change Must not exceed the validator's commission-max-change-rate which is maximum.Must be between 0 and the validator's commission-max-rate.Note: The commission-rate value must adhere to the following rules: Please note that some parameters such as commission-max-rate and commission-max-change-rate cannot be changed once your validator is up and running. This is how you can add a logo to your validator profile. The Keybase API allows us to retrieve your Keybase avatar. It's a cryptographically secure method of verifying your identity across multiple online networks. When using Keybase, -identity should be populated with a 16-digit string that is generated with a keybase.io (opens new window) account. The -identity can be used as to verify identity with systems like Keybase or UPort. 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. The specifies which validator you are editing. 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. Make sure to provide input for every flag below.

This info is to identify your validator, and will be relied on by delegators to decide which validators to stake to. You can edit your validator's public description. You can confirm that you are in the validator set by using a third party explorer like Mintscan (opens new window). Users are able to delegate to inactive validators (those outside of the active set) using the Keplr web app (opens new window). It's possible that you won't have enough ATOM to be part of the active set of validators in the beginning. A min-self-delegation of 1000000 means your validator will never have a self-delegation lower than 1atom Min-self-delegation is a stritly positive integer that represents the minimum amount of self-delegated voting power your validator must always have.

Keybase api