> 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.md).

# 2. TECHNICAL ARCHITECTURE

RealmScale is designed as a modular Layer 3 execution environment optimized for autonomous, high-frequency, and strategy-driven game worlds. Rather than extending general-purpose blockchain execution, RealmScale introduces a specialized architecture that separates game execution, proof generation, and final settlement into distinct layers. This separation allows the system to achieve Web2-grade performance while preserving cryptographic verifiability and decentralization.

At a high level, the RealmScale stack consists of four layers:

1. Client Layer – player interaction and local state handling
2. Execution Layer (ZK-ECS) – deterministic game logic and state transition definition
3. Proving Layer – decentralized generation of validity proofs
4. Settlement Layer (Base) – final state verification, data availability, and asset anchoring

Each layer has a clearly defined responsibility and minimal trust assumptions, ensuring that complexity is isolated rather than compounded.


---

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