> For the complete documentation index, see [llms.txt](https://docs.maalscan.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maalscan.io/who-is-a-validator.md).

# Who is a validator?

A validator is a participant in the MaalChain network who locks up $MAAL coins in the Maal Validator DAO and takes active part in MaalChain governance via the DAO. Validators stake their $MAAL coins as collateral to work for the security of the network and in exchange for their service, earn rewards from the validator DAO. The onus of running the node on behalf of the validators lies with Maal Data Labs.

Rewards are distributed to all validators in DAO proportional to their Maal Coins staked half yearly distributed to the wallet which holds the Validator DAO NFT. User reward balance gets updated in the DAO contract which is referred to while claiming rewards.

For more details please refer to [Maal Validator DAO](/maal-validator-dao.md) section.


---

# 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.maalscan.io/who-is-a-validator.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.
