> 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/3.-the-serverless-network-topology.md).

# 3. THE SERVERLESS NETWORK TOPOLOGY

#### 3.1 From Centralized Servers to Decentralized Operators

Traditional online games rely on centralized server infrastructure operated by the developer or a cloud provider. These servers are responsible for executing game logic, resolving conflicts, maintaining world state, and broadcasting updates to clients. While effective for Web2-scale performance, this model introduces a single point of failure: when servers are shut down—due to cost, regulation, or company dissolution—the game world ceases to exist.

RealmScale eliminates this dependency entirely by replacing the concept of a centralized “game server” with a decentralized network of Operators, referred to as Prover Nodes. These nodes collectively assume responsibility for executing game logic and validating state transitions, without any single node being privileged or authoritative.

In this topology, the “server” is no longer a machine or organization, but an emergent property of the network itself.

***

#### 3.2 Prover Nodes and Deterministic Execution

When a player submits an action (e.g., movement, combat, crafting), the input is broadcast to the Prover Network rather than sent to a central authority. Prover Nodes independently execute the corresponding game logic using the immutable ZK-ECS ruleset. Each node computes the resulting state transition and generates a Zero-Knowledge Proof attesting that the transition is valid according to the game’s rules.

Because execution is deterministic and the rules are publicly defined, honest Prover Nodes will converge on the same state transition. The network aggregates these results, selects a valid proof, and forwards it for settlement on Base.

This design ensures that:

* No single node can arbitrarily modify the game state
* Incorrect or malicious execution is rejected cryptographically
* The integrity of the world is preserved even under adversarial conditions

***

#### 3.3 Serverlessness as Permanence

A defining consequence of this topology is permanence. In conventional games, the longevity of a world depends on continued financial and operational support from its creators. In RealmScale, the game logic is immutable, public, and executable by any Prover Node willing to participate.

As long as at least one honest Prover Node remains online, the game world continues to function.

This gives rise to a new category of digital systems: Autonomous Worlds and Perma-Games—worlds that exist independently of their creators, in the same way that a blockchain exists independently of its founding team. The shutdown of a studio does not terminate the world; it merely removes one participant from the network.

***

#### 3.4 Incentives, Fault Tolerance, and Network Resilience

The Prover Network is designed to be permissionless and economically incentivized. Operators are rewarded for generating valid proofs and penalized for submitting incorrect or malicious results. This creates a self-stabilizing system where correctness is aligned with economic incentives.

Furthermore, the decentralized topology provides inherent fault tolerance:

* Nodes can join or leave the network without coordination
* Geographic and jurisdictional diversity reduces systemic risk
* Network capacity scales horizontally with demand

This architecture transforms game execution from a fragile service into a resilient, decentralized infrastructure layer.


---

# 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/3.-the-serverless-network-topology.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.