> 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.md).

# About Validators

Introduction to Chiliz Chain's PoSA consensus, Main Validators, Candidate Validators, slashing mechanisms, and delegator roles in block production.

Chiliz Chain relies on the Proof of Staked Authority (PoSA) consensus mechanism, designed to ensure fast block times and cost-efficient transactions.

Advanced security features, including double-sign detection and slashing mechanisms, maintain the integrity, stability, and finality of the chain.

This consensus mechanism is primarily managed by two key roles:

* the Validators, who are a critical part of the chain. They create and validate blocks in turns.
* the Delegators, who allocate their CHZ to the validators' pools in order to participate in the governance of the chain and earn reward.

In Chiliz Chain, there is a set maximum of block-creating validators. There can also be an unlimited amount of active validators which are not creating blocks, but are in the queue in case a block-creating validator goes offline or gets "jailed".


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.