> 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/overview.md).

# Overview

What WALL STREET is, how it is built, and what state it is in.

<img src="https://934907292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgl9HiYsbYNCbL7plUYQv%2Fuploads%2Fgit-blob-2793410d6c3a822da5b27af3e54c1f3755d02f71%2Fbull-coin.png?alt=media" alt="The $STREET coin: a bull over three rising candles" width="120">

**WALL STREET** is a server-authoritative, play-to-earn browser MMO about a 1990s-flavoured trading floor. Ticker **$STREET**, an SPL token on **Solana** — mint not yet published. Tagline: *Trade or be traded.*

![Architecture](https://934907292-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgl9HiYsbYNCbL7plUYQv%2Fuploads%2Fgit-blob-85cf335e1ff794969b0f4a595c2e214d932d82b0%2Farchitecture.svg?alt=media)

## The thesis in five lines

1. **PvP is the economy.** Every dollar a player earns comes from a matched counterparty, a bounded NPC pool with a sink, or a fee-taking venue. There is no faucet, so the economy does not depend on new money arriving to pay old money.
2. **Sinks exceed faucets 12.5× at every population**, and the ratio is constant by construction rather than by tuning.
3. **Nothing purchasable changes a number.** No pay-to-win surface exists, and a test fails the build if one appears — which is what keeps the retention curve honest.
4. **The outward rails ship disarmed.** The game never mints, custodies or transfers a security. A licensed venue settles claims and owns KYC.
5. **The build is real.** Client and server both build and deploy on one command each; migrations, load gates and smoke suites run in CI.

## What a reader should take from each page

| Page                                                                          | The question it answers                                       |
| ----------------------------------------------------------------------------- | ------------------------------------------------------------- |
| [The product](/wall-usdstreet-on-rh/investors/the-product.md)                 | What is the game, and why would somebody play it for a year?  |
| [The economy](/wall-usdstreet-on-rh/investors/the-economy.md)                 | Does it hold together at 100, 500 and 2,500 players?          |
| [The two rails](/wall-usdstreet-on-rh/investors/the-rails.md)                 | What is the token, what is a claim, and what is the boundary? |
| [Technology](/wall-usdstreet-on-rh/investors/technology.md)                   | What is actually built, and on what?                          |
| [Risk and compliance](/wall-usdstreet-on-rh/investors/risk-and-compliance.md) | What can go wrong, and what is already in front of it?        |
| [Status and roadmap](/wall-usdstreet-on-rh/investors/status.md)               | What state is it in today?                                    |

{% hint style="warning" %}
This documentation describes a game and its engineering. It is not an offer, a solicitation, a prospectus or investment advice, and no return of any kind is promised. Play earns claims; a licensed partner settles the eligible ones.
{% endhint %}


---

# 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/overview.md?ask=<question>&goal=<endgoal>
```

`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.
