> For the complete documentation index, see [llms.txt](https://docs.pretzel.build/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pretzel.build/pop-guardian-nodes/how-pop-guardian-nodes-work.md).

# How PoP Guardian Nodes work?

<figure><img src="/files/haWOUwheXuPnWzVKgfyt" alt=""><figcaption><p>PoP Nodes</p></figcaption></figure>

A **PoP Guardian Node** within Pretzel's **PoP Framework** is responsible for monitoring and alerting the network to any discrepancies in transactions or state transitions. These nodes act as a safeguard, ensuring that all operations within the rollup adhere to the highest standards of precision and security. Their role is to maintain the integrity of the Pretzel network, ensuring smooth and accurate game state transitions across the ecosystem.

Transactions are ingested and executed by the **Pretzel EVM,** ensuring efficient and scalable operations within the Layer 2 framework.

* **Compression**: All state transitions are optimistically rolled up and Merkle-compressed. Transactions are aggregated into a Merkle tree, reducing data size and enhancing throughput.
* **Proof Generation**: For each slot, a proof is generated by each grid instance. For every block, the corresponding root state hash is committed. Each new root represents the updated state for that block or slot.
* **Proof Commitment**: Proofs are committed to the PoP network to prevent any state collisions. It computes light sampling with fraud proofs and forwards all proofs to the verifier program on Berachain for further validation.


---

# 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.pretzel.build/pop-guardian-nodes/how-pop-guardian-nodes-work.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.