> 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/status.md). # Status and roadmap What exists today, what is gated, and what comes next. ## Today | Area | State | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Client | Builds and deploys on one command; production build refuses an unsafe server URL | | Server | Worker + per-zone Durable Objects + D1 bundles clean; migrations apply cleanly end to end | | The city | Eight quarters, four trading posts, the annunciator, authored towers, walkable estates | | The market | 24 symbols, order-flow impact, partial fills, margin, borrow, a seven-strike options chain | | PvP | Counterparty matching, corners, the pit (with house locals), THE CURB and the house man, THE OPEN FLOOR in rounds, THE PHONE ROOM | | Contests | COMPOSURE: pressure, a public read, knockdowns, three physical pieces and no more | | TAKE ONE PUBLIC | **Wired and hardened.** A desk on the plaza, `listing` on the wire, seniors file, the books persist, the retained float is charged, the lockup runs | | Ladder & regulator | Eight positions with gates; five-step SEC exposure with HALTED as the worst outcome | | Claims | Full state machine, gates, caps, holds, expiry, cash fallback, settlement preference | | THE REAL BOARD | **Live, and in venue mode.** `SETTLEMENT_ALLOWLIST` publishes AAPL, MSFT and NVDA, so eligibility gates on the venue's answer. The street's own board is the unpublished state | | Settlement path | **Cash only.** The stock rail was built on the old chain; with $STREET and identity on Solana and no Solana pools for those names, a claim settles as cash at the published rate — and the fill is switched off in the deployed build regardless | | The chain | **Solana.** $STREET is an SPL token and Phantom is the wallet and the identity; the Robinhood Chain / MetaMask path is removed, not deprecated | | Rail 1 — $STREET | **No mint.** No contract address is published, the mainnet flag is `0`, and an unconfigured mint resolves to credits-only. The token is sold as seats and skyline, never as an earn | | Rail 2 — fulfillment | **Disarmed.** Both paths refuse: the DEX fill is off and built for the old chain, and the partner adapter is a stub until venue credentials exist | | Infrastructure | **Provisioned.** This game's own D1 carries all 59 migrations, and its Worker is deployed against it | ## Gated on the owner, not on engineering 1. A funded, published bridge reserve, and the decision to throw the one switch that makes a transfer real. 2. A signed agreement with a licensed settlement venue, with their KYC in front of eligibility — the allowlist that puts the desk in venue mode is already published, so this is the gap between a configured rail and an armed one. 3. Counsel in the jurisdiction each rail operates from. 4. The reserve sized against the worst-case rows in [the economy](/wall-usdstreet-on-rh/investors/the-economy.md), not against a projection. ## Next * The prediction book. * Block-order raids. * A flash crash you can pay for. *** > Nothing on this page is an offer, a solicitation or investment advice, and no return of any kind is promised. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://reverie.gitbook.io/wall-usdstreet-on-rh/investors/status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.