> For the complete documentation index, see [llms.txt](https://docs.helalabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helalabs.com/hela-node/hela-guardian-node/how-guardian-node-works.md).

# How Guardian Node works?

The Hela Guardian Node network comprises up to 50,000 decentralized nodes tasked with monitoring and validating the health and performance of various servers and systems within the Hela ecosystem.

Each node operates independently, interacting with designated machines and tasks, and reporting its findings to a central backend system.

This data is subsequently integrated into the Guardian Node Smart Contract, providing a real-time snapshot of the network's health.

**Guardian Node vs. Validator Node vs. Client Node**

| Feature                  | Validator Node                 | Guardian Node                              | Client Node                             |
| ------------------------ | ------------------------------ | ------------------------------------------ | --------------------------------------- |
| **Produces Blocks**      | ✅ Yes                          | ❌ No                                       | ❌ No                                    |
| **Validates Consensus**  | ✅ Yes                          | ✅ Yes (indirectly, by checking validators) | ❌ No                                    |
| **Supports ParaTime**    | ✅ Yes                          | ✅ Yes                                      | ✅ Yes                                   |
| **Slashing Risk**        | ✅ Yes                          | ❌ No (only watches)                        | ❌ No                                    |
| **Hardware Requirement** | High (CPU, RAM, uptime)        | Medium                                     | Low                                     |
| **Best For**             | Stakers, heavy infra providers | Security-conscious devs, watchdogs         | dApp developers, explorers, light users |


---

# 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.helalabs.com/hela-node/hela-guardian-node/how-guardian-node-works.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.