> 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/4.-privacy-and-strategy.md). # 4. Privacy and Strategy #### 4.1 Transparency Constraints in Public Execution Public blockchains enforce global state transparency as a core security property. Every state transition, input, and output is observable by all participants. While this model is well-suited for financial ledgers, it introduces structural constraints for strategy-driven applications. In games where hidden information is essential—such as RTS, TCG, Poker, or social deduction—full state visibility collapses information asymmetry and invalidates gameplay. Under a fully transparent execution model, adversaries can extract private game information directly from on-chain data, enabling look-ahead attacks, strategic leakage, and automated exploitation. This forces developers to choose between centralizing execution off-chain or simplifying game mechanics to remove hidden state entirely. Both outcomes undermine the goals of decentralization and autonomy. RealmScale treats this as a protocol-level problem rather than an application-level workaround. *** #### 4.2 Separation of State Validity and State Visibility RealmScale introduces a strict separation between state validity and state visibility. The protocol enforces that all state transitions are valid according to the game rules, while allowing portions of the state to remain undisclosed to the public network. Game state is partitioned into: * Public State: globally visible and directly settled on Base. * Private State: required for rule evaluation but not publicly observable. Private state is not written to the ledger in plaintext. Instead, it is committed to the global state using cryptographic commitments. These commitments bind the private values to the game state without revealing their contents, enabling verification without disclosure. *** #### 4.3 Zero-Knowledge Action Verification Actions that depend on private state are accompanied by zero-knowledge proofs generated by the client or Prover Nodes. Each proof attests that: 1. The action is consistent with previously committed private state. 2. All game rules and constraints are satisfied. 3. The resulting state transition is correctly derived. Verifiers validate the proof without learning the underlying private inputs. Upon successful verification, the protocol updates the corresponding state commitments and advances the world state. Invalid or malicious actions cannot be settled, as they cannot produce a valid proof. This mechanism guarantees rule enforcement without revealing strategic information. *** #### 4.4 Protocol-Enforced Information Revelation Information disclosure in RealmScale is governed by protocol-defined reveal conditions rather than client-side conventions. Reveal logic is encoded as part of the game’s execution rules and evaluated within the ZK-ECS framework. When predefined conditions are met—such as visibility range, detection mechanics, or resolution phases—the protocol requires the corresponding private state to be revealed or partially disclosed. Until these conditions are satisfied, private state continues to influence execution while remaining hidden from other participants. By enforcing reveal semantics at the protocol level, RealmScale prevents selective disclosure, withholding, or manipulation of information, even in adversarial environments. *** #### 4.5 Strategic Integrity Without Trusted Servers Because all execution validity is enforced through zero-knowledge verification, RealmScale does not rely on centralized servers, trusted operators, or secure enclaves to preserve privacy. Strategic integrity is guaranteed by cryptography rather than trust assumptions. This design enables entire classes of games previously incompatible with public blockchains, while maintaining decentralization, verifiability, and performance. Privacy becomes a first-class execution primitive, allowing autonomous worlds to support strategy, deception, and partial observability without sacrificing trustlessness. --- # 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/4.-privacy-and-strategy.md?ask= ``` 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.