> For the complete documentation index, see [llms.txt](https://docs.realmscale.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmscale.vip/2.-technical-architecture/2.3-proof-aggregation-and-execution-finality.md).

# 2.3 Proof Aggregation and Execution Finality

Given the high frequency of in-game actions, individual proofs for every action would be inefficient to settle directly on Layer 2. RealmScale addresses this through recursive proof aggregation.

Prover Nodes aggregate thousands of individual state transitions into a single recursive validity proof that represents a batch of game execution steps. This aggregated proof certifies that all included transitions are valid and correctly ordered according to the ZK-ECS ruleset.

Recursive aggregation achieves three critical goals:

* Scalability: Proof verification costs remain constant regardless of the number of underlying actions
* Latency reduction: Game execution can proceed continuously without waiting for individual settlements
* Deterministic finality: Every batch submitted for settlement is mathematically verified before acceptance

This model allows RealmScale to function as a high-throughput execution environment without sacrificing cryptographic guarantees.


---

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

```
GET https://docs.realmscale.vip/2.-technical-architecture/2.3-proof-aggregation-and-execution-finality.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.