Useful Commands
A list explaining some useful commands along with their outputs.
Slashing Params List
sentinelhub q slashing params
The output looks like
Example Output
downtime_jail_duration: 600s
min_signed_per_window: "0.050000000000000000"
signed_blocks_window: "10000"
slash_fraction_double_sign: "0.050000000000000000"
slash_fraction_downtime: "0.000100000000000000"
It basically explains the rules to avoid being jailed.
- There is a window of 10k blocks (signed_blocks_window).
- Any validator needs to sign 5% (min_signed_per_window) of the blocks in this window (i.e., 500 blocks within any 10k blocks window).
- If the percentage of signed blocks falls below 5, the validator is jailed for downtime.
- If a validator is jailed for downtime, they are slashed 0.01% (slash_fraction_downtime) of their stake and can be unjailed after 10 minutes (downtime_jail_duration).
- If a validator is jailed for a double sign, they are slashed 5% (slash_fraction_double_sign) and cannot unjail ever.
Signing Info
This command retrieves the signing information of the validator using its consensus public key
sentinelhub query slashing signing-info $(sentinelhub tendermint show-validator)
Upon execution, you will receive an output similar to the following:
Example Output
address: sentvalcons1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
index_offset: "11513"
jailed_until: "1970-01-01T00:00:00Z" #(if different from this, means you are jailed)
missed_blocks_counter: "5" #how many blocks you skipped within the 10k blocks window
start_height: "9982764"
tombstoned: false #if true, means you double signed
Please be aware that if you are utilizing TMKMS, since it typically resides on a separate machine, the aforementioned command will not function as expected. To ensure its execution, you must navigate to ping.pub, extract the Consensus Public Key, and subsequently paste it into the following command for execution:
sentinelhub query slashing signing-info '{"@type":"/cosmos.crypto.ed25519.PubKey","key":"M2sRH0zuP/2wqnDR7lkK/Qbb+CZdWHYYRjhyM9yX0IY="}'
Validator & Sync Info
This command provides comprehensive information regarding your validator, including its synchronization status and other relevant details.
curl --silent "http://localhost:26657/status" | jq -S
When you receive the output, check the following fields:
sync_info.catching_up #if true, it means your node is not synced and therefore it will not sign blocks until it catches up with the rest of the chain
sync_info.latest_block_time #the value should be close to the current time. If it's not, that means your node is also out of sync and won't be able to sign blocks (or the chain has halted).
validator_info.voting_power #If the value is 0, this node is not an active validator, either because you are not in the active set, or because you are jailed, or because the priv_validator_key does not match the validator key
Connected Peers
This command provides you with the list of peers to which the validator is currently connected.
curl -sS http://localhost:26657/net_info | jq -r '.result.peers[] | "\(.node_info.id)@\(.remote_ip):\(.node_info.listen_addr)"' | awk -F ':' '{print $1":"$(NF)}'
Example Output
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:50656
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:26796
[email protected]:26656
[email protected]:26656
[email protected]:26706
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:33656
[email protected]:23956
[email protected]:26656
[email protected]:23956
[email protected]:23956
[email protected]:26656
[email protected]:23956
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:53656
[email protected]:15100
[email protected]:26706
[email protected]:26656
[email protected]:26656
[email protected]:36656
[email protected]:26656
[email protected]:26796
[email protected]:16646
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:26656
[email protected]:17256
[email protected]:26656