> For the complete documentation index, see [llms.txt](https://railhood.gitbook.io/railhood-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://railhood.gitbook.io/railhood-docs/roadmap.md).

# Roadmap

One rule sets the order: crowd depth first. Every participant makes every other participant harder to trace, so anything that grows the pool ships before anything that doesn't.

### Now (LIVE)

* The ETH pool on Robinhood Chain — off-market entries and exits in six standard sizes (0.001 – 100 ETH), 0.25% fee each side.
* MCP server + command-line tool for agents: `pool_stats`, `shield`, `unshield`.
* Gasless exits through the settlement agent — your wallet never appears as the sender.

### Next

* Stablecoin pools and in-pool private transfers — pay counterparties without surfacing on the tape at all.
* Screening at the door — sanctions checks on every entry.
* Settlement receipts — zero-knowledge proof of clean provenance on exit.
* Viewing keys and selective disclosure, including off-market balance reads and fee quoting for agents.
* Agent SDK & policy engine — per-agent spend caps, so an injected agent can't spend past its allowance.
* x402 pay-per-call extras: priority settlement lane, receipt exports.

### Later

* Off-market treasuries — fund a fleet of agents from one pool balance, viewing key per agent.
* Agent trust infrastructure on Robinhood Chain (ERC-8004 registries).
* Private cross-chain settlement.
* Post-quantum migration as NIST-standardized components mature.

Live means live. Next means being built. Later means designed, not scheduled.


---

# 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://railhood.gitbook.io/railhood-docs/roadmap.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.