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

# RGO Token Structure

## Total Supply

**200,000,000 RGO**

*(Fixed supply. No additional issuance.)*

### Token Allocation

#### 1. Ecosystem & Community — 40%（80,000,000 RGO）

Supports long-term ecosystem development, community programs, Shorts engagement, and platform-wide activities.

#### 2. Platform Treasury — 30%（60,000,000 RGO）

Reserved for long-term platform development, operations, and strategic expansion.

#### 3. Liquidity & Market Making — 15%（30,000,000 RGO）

Provides the liquidity required for initial market stability and upcoming exchange listings.

#### 4. Core Contributors (Team) — 15%（30,000,000 RGO）

Allocated to contributors across engineering, product, design, operations, and growth. 

**RGO maintains a disciplined release structure designed to keep early circulating supply low while supporting healthy long-term ecosystem growth.**


---

# 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://rgo.gitbook.io/rgo/official-token/rgo-token-structure.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.