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

# What comes next

Rooter ships in an order, not on a calendar. Each step starts when the one before it has been checked. No step below has a date, and none will be given one until it is done.

**1. This document and the token.** This document, the site, and $ROOTR on Robinhood Chain. The token address, supply and treasury addresses go on the Addresses page.

**2. The build.** The contracts in [Under the hood](/whitepaper/under-the-hood.md) are written and tested against a copy of Robinhood Chain and on its public testnet. An outside audit of the fee hook, the escrow, the Rooter Pool and the liquidity lock, with the full report published. Deployment behind the pause, exercised with the team's own money on real coins, every contract verified on the explorer, every address published.

**3. Rooting opens.** ETH-quoted coins for everyone. The Rooter Pool, the finder's fee, root links and sweeps are live from the first coin. Every fee, claim, sweep and payout is on the chain, and a public log shows them.

**4. Root in their stock.** The allowed list opens with the first Robinhood Stock Tokens, with the eligibility rules in [Root in their stock](/whitepaper/root-in-their-stock.md) applied in the interface.

**5. Matchups and rooter weight.** Sponsored matchups and the weekly featured one. $ROOTR staking for Rooter Pool weight, written up on its own and audited before it ships.

Three things are not on this list and never will be: a way to withdraw locked liquidity, a way to reach an account's escrow without its claim, and a fee above three percent.


---

# 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://rooter-3.gitbook.io/whitepaper/what-comes-next.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.