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

# Types of Nodes

ChainVast supports two main types of nodes within its network:

* **Validator Nodes**\
  These are responsible for producing, verifying, and finalizing blocks within the ChainVast blockchain. Validators participate in the consensus process, ensuring network integrity and transaction finality.
* **Full Archive Nodes** *(optional for advanced data querying and analytics)*\
  These maintain a complete history of all blockchain states, allowing developers and analytics providers to access historical data without participating in block production.

> **Note:** Validator nodes require staking INVAST tokens and active uptime to maintain network trust


---

# 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.invast.io/node-and-validator-operations/types-of-nodes.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.
