> For the complete documentation index, see [llms.txt](https://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/technical-architecture/x1-ecochain-validators.md).

# X1 EcoChain Validators

#### X1 EcoChain Validators ensure:

* **Transaction Validation –** confirming transactions.
* **Block Creation –** adding new blocks to the blockchain.
* **Consensus Participation –** ensure consistency among all participants.
* **Network Security –** preventing attempted attacks and adhere to network protocols.

Validators receive **90%** of all commissions and **20%** of the operational part (smart contracts, token listing, etc.).

To obtain Validator status, a participant must own an X1Node activated with API key, acquire a Validator API key, and stake assets.

The first batch of 500 validator API keys has been fully sold.

The next batch will be announced at a later date.

If a validator no longer meets the required conditions, such as by unstaking their assets or downtime, their Validator status is revoked.

Anyone can become a validator by fulfilling the necessary requirements.


---

# 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://x1ecochain.gitbook.io/x1-ecochain-tech-whitepaper/technical-architecture/x1-ecochain-validators.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.