> For the complete documentation index, see [llms.txt](https://docs.runnersrh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runnersrh.app/getting-started/how-it-works.md).

# How It Works

The lifecycle of a RUNNERS coin, from launch to claim.

Every RUNNERS coin goes through the same five stages. The template is fixed, so no coin has an unfair structural advantage over another.

## The five stages

### 1. Launch

Pick a **name**, **ticker**, and **image**, then deploy. On Robinhood Chain, every launch uses the same fixed template — same supply, same fee, same vesting.

### 2. Liquidity

**30% of the supply** seeds a Uniswap V3 liquidity pool.

{% hint style="success" %}
**The liquidity is locked forever.** It cannot be pulled — the classic "rug pull" is off the table.
{% endhint %}

### 3. Vesting

**70% of the supply** is reserved for the creator and released gradually through a vesting schedule.

* **90-day cliff** — nothing unlocks in the first three months
* **24-month linear** — after the cliff, releases smoothly over two years

This aligns the creator with the **long-term health** of the coin instead of an instant dump.

### 4. Trading

The coin is **immediately tradable** from block one. Every trade pays a small fee that is split between the creator and the platform.

### 5. Claiming

Creators claim their **trading fees** and **vested supply** from the dashboard whenever they want. The platform pays the gas for claims — you don't need to hold anything to collect what you've earned.

***

## Visual lifecycle

```
   LAUNCH ──▶ LIQUIDITY (30%) ──▶ TRADING ──▶ FEES ──▶ CLAIM
                    │                            │
                    ▼                            ▼
              LOCKED FOREVER              80% → CREATOR
                                          20% → PLATFORM

              CREATOR (70%)
                    │
                    ▼
            90d cliff ── 24mo linear vest ──▶ CLAIM
```

***

{% hint style="info" %}
**Next up:** See the exact numbers in [**Fixed Tokenomics**](/tokenomics/fixed-tokenomics.md).
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.runnersrh.app/getting-started/how-it-works.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.