> 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/core-functionality.md).

# Core functionality

Guardian Nodes perform four main functions:

1. **Server Health Monitoring**
   * Track CPU usage, consumption, disk usage, network latency, and uptime.
   * Ensure critical HeLa infrastructure remains operational
2. **Data Validation**
   * Verify accuracy and integrity of data across the network
   * Prevent errors, inconsistencies, and fraudulent activity
3. **Anomaly Detection**
   * Detect unusual behavior or failures in real time
   * Report anomalies to backend systems for further action
4. **Reporting & Rewards**
   * Nodes submit their findings to a centralized backend, which processes the data and updates the Guardian Node Smart Contract. 
   * Contract maintains a record of each node's performance, serving as the basis for reward distribution and performance evaluation.

## Interaction with the HeLa Ecosystem

Guardian nodes interact with various components of the HeLa ecosystem:

* Servers: Nodes directly communicate with the servers they are assigned to monitor.
* Backend System: Nodes transmit collected data to the backend for processing and analysis.
* Guardian Node Smart Contract: Nodes contribute to the updating of the smart contract with their findings.
* Other Nodes: Nodes can potentially collaborate with other nodes to enhance monitoring capabilities or share information.<br>


---

# 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/core-functionality.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.