> For the complete documentation index, see [llms.txt](https://realmatwar.gitbook.io/realmatwar-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://realmatwar.gitbook.io/realmatwar-docs/realm-at-war-handbook/help-and-safety/trust-and-safety.md). # Trust & Safety Real money and real tokens are involved, so it's worth being completely clear about how they're handled. The whole design follows one principle: **the game should never be in a position to take or lose your money.** Here's how that's enforced. ## Your Purchase Is Split at the Source When you buy Crowns, you don't pay the game and trust it to forward the money. Your payment is split **inside the purchase transaction itself** — 70% to the Prize Pot wallet and 30% to the Revenue wallet — and both payments go **directly** to those wallets on-chain. The game server isn't a middleman holding your funds. It simply **reads the blockchain**, confirms your payment actually landed (the right amounts in the right wallets, with no errors), and then credits your Crowns. If the payment didn't happen, no Crowns; the server can't be tricked into crediting a purchase that wasn't made, and it can't lose money it never holds. ## Crediting Is Keyless To credit your Crowns or record your $REALM, the server only ever *reads* and verifies on-chain data. It does **not** hold the keys to any funds and it does **not** sign transactions that move money. There's simply no private key sitting on the public game server that could be stolen to drain anything. ## Payouts Are Sent by an Isolated Signer Paying out prizes obviously *does* require sending tokens — so that job is deliberately kept **off** the game server and handed to a small, separate, isolated payout worker. * The game server's only role in payouts is to **publish the list** of who is owed what (an auditable batch) and to mark it settled once it's done. It never sends the tokens. * A **separate signer**, running on its own, holds the Prize Pot's key in its own private environment — never in the game's code, never in the browser, never in this repo. It reads the batch, sends the $REALM, confirms it landed, and tells the server it's settled. * That signer runs with safety rails: a **dry-run mode** to preview a batch before anything is sent, and **sanity caps** on the most it will ever pay in one run or to one wallet. It only settles payments it has actually confirmed. The result: the one key that can move the pot lives in exactly one isolated place, used for exactly one job, with guardrails — not scattered across the system. ## Your Wallet Stays Yours Connecting your wallet to play uses a **signature** to prove you own it — nothing more. The game never asks for your seed phrase or private key, and it can't move anything *out of* your wallet. Connecting only ever lets the game (a) know which realm is yours and (b) know where to **send** your $REALM. Money flows *to* you, never *from* you. And because your realm is tied to the wallet you proved you own, **nobody else can log into your realm** by guessing an address — the game checks the cryptographic proof on every connection. ## The Pot Can't Be Drained Finally, a structural protection worth repeating from [The Prize Pot & Payouts](/realmatwar-docs/realm-at-war-handbook/economy-and-rewards/the-prize-pot-and-payouts.md): every payout is a **percentage of the current pot**, so payouts can never exceed what's in it, and the pot can never be emptied to zero by the prize logic. The economy is incapable of promising more than it holds. --- # 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://realmatwar.gitbook.io/realmatwar-docs/realm-at-war-handbook/help-and-safety/trust-and-safety.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.