Onboard Process

• [ ] complete validator intake form
• [ ] setup testnet validators, follow steps
  • [ ] (optional, but strongly recommended) set up Node Monitoring
  • [ ] get stake delegated from foundation (reach out to us via email or discord)
• [ ] setup mainnet validator, follows steps
  • [ ] (optional, but strongly recommended) set up Node Monitoring
  • [ ] get stake delegated from foundation (reach out to us via email or discord)

Setting up a Validator

1. Run Axelar FullNode
   1. Download binary and configure node
   2. Startup node, wait for it caught up to the latest block height, you can either
      1. Fast track, use blockchain snapshot to sync to latest block
      2. Sync from genesis block and follow the upgrade path
2. Become a Validator by following the steps https://docs.axelar.dev/validator/setup/overview#steps-to-become-a-validator

Node Monitoring

Please read our guidelines and recommendations on monitoring a Validator or Node

Its highly recommended that alerts are setup around following prometheus metrics from a validator node

• https://docs.axelar.dev/validator/operations/monitoring#consensus-height
• https://docs.axelar.dev/validator/operations/monitoring#p2p-peers

Validators - Messaging Scheme

Setup pagerduty or other internal alerting scheme following this messaging scheme:

https://bright-ambert-2bd.notion.site/Validators-Messaging-Scheme-Public-Page-0e5021d084eb4824bdf3216e59d3c39a

Read Slashing Conditions for Downtime and Double-Signing

Execute following CLI on the machine hosting validator or node

$ axelard q slashing params

Output should be something like

downtime_jail_duration: 7200s
min_signed_per_window: "0.500000000000000000"
signed_blocks_window: "35000"
slash_fraction_double_sign: "0.020000000000000000"
slash_fraction_downtime: "0.000100000000000000"