Validator Checklist

Complete checklist for Chiliz Chain validator operators: stake requirements, node setup specs, registration steps, ongoing obligations, and exit procedures.

This page gathers everything a validator operator needs to do, from first decision to eventual exit, in one checklist. Each item links to the detailed guide.

Phase 1: Before you apply

• Confirm you can stake a minimum of 10 million CHZ.

• Decide whether you will run your own node or use a third-party service.

• Understand how rewards and commissions work.

• Understand slashing risks: missed blocks cost you the epoch's rewards (Level 1), and extended downtime leads to a 4-epoch jail (Level 2).

• Be aware that your application is subject to a vote by the existing validator set.

Phase 2: Node setup

Full instructions: Running a Validator node

• Server meets the system requirements: 2+ CPU cores, 4+ GB RAM, SSD with at least 300 GB free, 10 Gbps network bandwidth.

• Docker Engine is installed.

• Validator address is created.

• The secret key file is backed up and the key file password is stored in password.txt. Never share the secret key with anyone.

• A node key hex is generated and set via --nodekeyhex (recommended, for a stable enode address).

• --nat=extip:<IP> is set to your server's public IPv4 address.

• The node runs with --syncmode=full and --gcmode=archive, and is fully synced with the chain.

Phase 3: Registration

Full instructions: How to Become a Validator

• Registration form submitted on the Chiliz Governance dApp: node address, stake amount (≥ 10M CHZ), commission rate.

• Governance proposal launched by an existing validator and approved by the validator set.

Phase 4: Ongoing operations

• Monitor your node's uptime: missed blocks lead to Level 1 slashing (lost epoch rewards).

• Know the unjail procedure in case your node gets jailed (Level 2 slashing).

• Keep your node software up to date with hard forks and code changes. Outdated validator nodes can disrupt the chain, and your rewards.

Phase 5: If you exit

• To stop validating entirely, follow the decommissioning steps: clean shutdown, unstaking (with cooldown), and deactivation on the Governance dApp.

• To hand the node over instead, use the "Change owner" procedure.