> For the complete documentation index, see [llms.txt](https://reverie.gitbook.io/wall-usdstreet-on-rh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reverie.gitbook.io/wall-usdstreet-on-rh/investors/risk-and-compliance.md). # Risk and compliance What can go wrong, and what is already in front of it. ## The boundary, stated plainly The game emits and records claims. The game never mints, custodies or transfers a tokenized equity: on the on-chain path it buys an existing token at market with treasury funds and sends it to the player's own wallet; on the partner path a licensed venue settles and owns KYC. Symbols, companies and indices in the simulation are invented. The only real tickers anywhere in the product are the three on the settlement allowlist — AAPL, MSFT and NVDA — and nothing in the simulation reads that table. **Today nothing settles into a security at all: every claim becomes cash at a published rate.** The stock rail exists but cannot fill — it was built for the chain the product has since left, and it is switched off in the deployed build. When it does fill, what it delivers is a tokenized stock token that trades 24/7 on a decentralised exchange, **not a NYSE share** — stated on the desk a player reads, not only in documentation. ## Register | Risk | What is already in front of it | | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Regulatory — the claim** | Both rails ship disarmed; arming each is gated on counsel in the settling jurisdiction and a signed agreement with a licensed venue whose KYC sits in front of eligibility | | **Regulatory — the token** | Testnet only, no mint, no treasury key in the tree; mainnet refused unless the owner sets an explicit flag, and the live state is reported truthfully by the health endpoints | | **Reserve exhaustion** | The budget is pre-funded and refuses rather than borrows. Worst case is *accrual stops*, never an unpayable obligation. The accrual rate is a table and steps down without a deploy | | **Farming and collusion** | A surveillance desk that reads patterns rather than trades; a 400-point daily cap per account; a 24-hour hold; idempotency keyed to the event; quarantine that earns nothing while still playing normally | | **A claim stranding** | Every claim below the settlement minimum, or refused by the venue, converts to in-game cash at a fixed published rate. No claim is ever stuck | | **Double accrual across zones** | The budget is reserved atomically in D1 with a conditional update, so two zones cannot both take the last points | | **Economy inflation** | No faucet by design; sinks exceed faucets 12.5× by construction, and the ratio tightens as the population grows | | **Pay-to-win drift** | A test fails the build if a purchasable item grows a stat, and a second asserts the seat gates access only | | **Fiction and IP drift** | A vocabulary test walks all authored prose and fails on inherited fiction; no real person, firm, film or brand appears in the game | | **Accidental writes to seed infrastructure** | An infrastructure guard blocks every deploy path while the configuration names a seed project, Worker or database | | **Custody and phishing** | The game never asks for a seed phrase or a private key; wallet interaction is a signature over a login string and nothing else | | **Content rating and distribution** | Nobody dies, by design. Contests run on COMPOSURE and end in a FOLD; exactly three physical pieces exist and a loss to one is a KNOCKOUT the character gets up from. The worst lasting outcome is being barred | | **Real names on the board** | The desk is in venue mode: three real tickers are published, so eligibility gates on the venue's answer — a linked wallet, the identity check, the jurisdiction — and a stale answer is a refusal. The unpublished state falls back to the street's own board of invented names, which needs no wallet and no identity check | | **A lookalike token** | Each name is pinned to its official contract address and a same-ticker impostor is refused by not being on the table; a test holds all three addresses | | **A bad fill** | The swap is quoted before it runs with a 1% slippage ceiling; no quote, no signature, or a reverted swap all end in cash at the published rate | | **Arming by accident** | The DEX fill is switched off in the build and a Solana wallet is refused before a swap is attempted, so the current behaviour of every settle is the cash path | | **A chain migration leaving stale promises** | $STREET and identity moved to Solana; the token has no mint, so the game runs on credits and the product says so rather than describing a token somebody could be sold | | **A faucet in the claim table** | One source — the campaign act — is a faucet, named as one. An act completes once and there is a fixed small number of them, so the lifetime total per account is bounded before a broker starts. House money (pit locals, the house man) earns nothing | ## The lines the product holds * Play earns claims; a licensed partner settles the eligible ones. * No stock, yield, return or amount is named in any marketing. * Nothing in the game is a solicitation to buy any security or token, and nothing in it is investment advice. * If a proposal cannot be described without claiming it makes a player better at trading, it does not ship. --- # 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, and the optional `goal` query parameter: ``` GET https://reverie.gitbook.io/wall-usdstreet-on-rh/investors/risk-and-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.