# How do HyperFuse Guardian Nodes Work?

Here is an example process for where HyperFuse plays the part in Sonic and HyperGrid ecosystem:

1. Transactions are ingested and executed by the Grid(Sonic SVM).
2. Compression – All state transitions are optimistically rolled up and Merkle compressed. Transactions are compressed and aggregated into a Merkle tree.
3. Proof Generation – A proof is generated by each grid instance for each slot. For each block, the corresponding root state hash is committed. A new root represents each block/slot.
4. Proof Commitment – Proofs are committed to the HSSN to avoid any state collisions. The HSSN serves as a validation layer for transactions processed by Grids. Light sampling with light fraud proofs is computed here, and the HSSN pushes all proofs to the verifier program on Solana for further validation.
5. HyperFuse observes and verifies HSSN state submission onto Solana. If an incorrect submission is proposed, it raises an alarm (by whatever means its operator chooses) so that others can intervene.

<figure><img src="/files/Ed1BSJAmIIy8Ebml6sbF" alt=""><figcaption><p>Sonic &#x26; HyperGrid Ecosystem Mapping</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://hyperfusedocs.sonic.game/introduction/how-do-hyperfuse-guardian-nodes-work.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.