Run a Validator
Last updated
Was this helpful?
Last updated
Was this helpful?
Make sure your server timezone configuration is UTC. Having a different timezone configuration may cause a LastResultsHash
mismatch error. This will take down your node!
Your node consensus public key (swaplandvalconspub...
) can be used to create a new validator by staking SwapLand tokens. You can find your validator pubkey by running:
To create your validator, just use the following command:
You can confirm that you are in the validator set by using a third party explorer.
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 certain flags, remember that the --from flag must be included to identify the validator to update.
Note: The commission-rate
value must adhere to the following invariants:
Must be between 0 and the validator's commission-max-rate
Must not exceed the validator's commission-max-change-rate
which is maximum % point change rate per day. In other words, a validator can only change its commission once per day and within commission-max-change-rate
bounds.
View the validator's information with this command:
In order to keep track of a validator's signatures in the past you can do so by using the signing-info
command:
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).
Your validator is active if the following command returns anything:
You should now see your validator in one of SwapLand explorers. You are looking for the bech32
encoded address
in the ~/.SLC/config/priv_validator.json
file.
NOTE
To be in the validator set, you need to have more total voting power than the 100th 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 SLCd
. 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 500
of the last 10000
blocks, or if they double sign.
If you got jailed for downtime, you can get your voting power back to your validator. First, if SLCd
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
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 1024
. SLCd
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 SLCd start
. If you are using systemd
or another process manager to launch SLCd
this may require some configuration at that level. A sample systemd
file to fix this issue is below:
The --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 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.