> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/learn/about-validators/validator-checklist.md).

# Validator Checklist

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](/learn/about-staking/staking-rewards.md).
* [ ] Understand [slashing risks](/learn/about-validators/about-validator-slashing.md): 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](/learn/about-validators/running-a-validator-node.md)

* [ ] 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](/learn/about-validators/how-to-become-a-validator.md)

* [ ] Registration form submitted on the [Chiliz Governance dApp](https://governance.chilizchain.com/staking): 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](/learn/about-validators/about-validator-slashing.md) (lost epoch rewards).
* [ ] Know the [unjail procedure](/learn/about-validators/about-validator-slashing.md) in case your node gets jailed (Level 2 slashing).
* [ ] Keep your node software up to date with [hard forks and code changes](/chiliz-chain-changelog/blockchain-code-changes.md). Outdated validator nodes can disrupt the chain — and your rewards.

## Phase 5: If you exit

* [ ] To stop validating entirely, follow the [decommissioning steps](/learn/about-validators/how-to-stop-being-a-validator.md): clean shutdown, unstaking (with cooldown), and deactivation on the Governance dApp.
* [ ] To hand the node over instead, use the ["Change owner" procedure](/learn/about-validators/running-a-validator-node.md#changing-the-owner-of-a-node).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.chiliz.com/learn/about-validators/validator-checklist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.