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

# $ROOTR

$ROOTR is the protocol's token. It has a fixed supply, it comes before the protocol, and its address is below.

## What it is

|          |                                                                                                                                        |
| -------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Supply   | 1,000,000,000, fixed. No mint function.                                                                                                |
| Order    | Before the protocol                                                                                                                    |
| Address  | [`0x308a36749bdac6e3c50a41299b3bdc564423590d`](https://robinhoodchain.blockscout.com/token/0x308a36749bdac6e3c50a41299b3bdc564423590d) |
| Chain    | Robinhood Chain, 4663                                                                                                                  |
| Treasury | Published on the Addresses page                                                                                                        |

You do not need $ROOTR to launch, trade, hold or claim a coin. None of the mechanics in this document require it.

## What it does

* **Buybacks.** Half of the protocol's net share of every trade fee is used to buy $ROOTR on the open market on Robinhood Chain and burn it. A contract does this; anyone can call it; the portion is a public parameter within the bounds in [The numbers](/whitepaper/the-numbers.md). This is what Rooter does with part of its revenue. It is not a floor and not a promise about price.
* **Matchup prizes.** The weekly featured matchup prize is paid in $ROOTR.
* **Governance.** $ROOTR holders decide what goes on the allowed list of stock quotes, parameter changes within their bounds, which matchup is featured, and how the operations share is spent. Decisions are proposed publicly and executed through the protocol multisig.
* **Later, rooter weight.** A future release will let $ROOTR be staked to increase a wallet's weight in the Rooter Pools of the coins it holds, up to a published cap. It will be written up as its own specification and audited before it ships.

## How Rooter is funded before the protocol earns

The launch venue's creator fee on $ROOTR trading is received by the Rooter treasury. That is what funds the build, the audits and the first matchups. The venue, the treasury addresses and their movements are published with the launch.

{% hint style="warning" %}
$ROOTR comes before the protocol so the protocol can be built in the open with a funded treasury. That means holding $ROOTR before the protocol is live is holding a position in this document, not in a running product. Read [Straight talk](/whitepaper/straight-talk.md) before you decide.
{% 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://rooter-3.gitbook.io/whitepaper/rootr-token.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.