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

# Validator Responsibilities

Validators on the Ramestta Network must:

* Ensure the network is available to users at all times.\
  \
  Ramestta nodes are measured by the number of checkpoint transactions they have signed.

  Polygon's testnet receives a checkpoint transaction approximately every 10-30 minutes. In the Ramestta network, all validators must sign the checkpoint transaction.

  In the absence of a signed checkpoint transaction, your validator node's performance will decrease.<br>
* Monitorize processes daily to find and address any issues that may arise from its activity.\
  \
  Regular checks of the services and processes associated with Heimdall and Bor are essential to ensure their smooth functioning. Nodes should perform these checks daily to identify and address any issues that may arise.

  Additionally, pruning of nodes should be carried out regularly to minimize disk usage. This involves removing unnecessary data from the blockchain to reduce the size of the blockchain data stored on the node's disk. This helps optimize the performance and efficiency of the node, ensuring it can operate at peak performance.<br>
* Ensure network is running correctly and efficiently.<br>
* Have between 5-10 MATIC on the signer address to sign and propose checkpoints.\
  \
  Minimum MATIC is needed to sign and propose checkpoint transactions on the Polygon mainnet. Not having a minimum amount of MATIC may result in delays in the transactions and checkpoint submission.<br>
* Be transparent with commission rates.<br>
* Report any issues and provide feedback or suggestions to us.


---

# 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.ramestta.com/welcome-to-ramestta/validate/validator-responsibilities.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.