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

# tokenomics

Every token launched on RobinFun shares the same transparent, market-cap-invariant economics. Creators can optionally customize the total supply and enable staking — the USD economics stay the same for every choice.

## Default parameters

| Parameter                              | Value             |
| -------------------------------------- | ----------------- |
| Total supply                           | 1,000,000,000     |
| Sold on the curve                      | 700,000,000 (70%) |
| Reserved for liquidity                 | 300,000,000 (30%) |
| Starting market cap                    | $4,000 (virtual)  |
| Graduation raise (trigger)             | $9,300            |
| Graduation market cap                  | ≈ $44,100         |
| Of the raise, to Uniswap liquidity     | $9,000            |
| Of the raise, to the protocol treasury | $300              |
| LP tokens at graduation                | 100% burned       |

No supply is allocated to a team. The 70% sold on the curve is the entire tradable supply; the 30% reserved for liquidity is paired with the raised ETH at graduation, and the resulting LP is burned.

## Choose your supply (optional)

Change nothing and your token launches with the defaults above. Or pick a **total supply between 10,000 and 1,000,000,000** (in increments of 10 tokens).

Market cap is invariant to supply: every choice starts at the same **$4,000** market cap and graduates at the same **≈ $44,100**. Supply changes the unit price per token, not the economics.

## Optional staking split

You can enable **staking** (a simple on/off choice) when launching. With staking enabled, the launch split becomes:

| Allocation             | Staking off | Staking on |
| ---------------------- | ----------- | ---------- |
| Bonding curve          | 70%         | 70%        |
| Uniswap liquidity (LP) | 30%         | 20%        |
| Staking rewards        | —           | 10%        |

The 10% staking allocation is carved out of the LP share — the **curve is untouched**, so the token still starts at $4,000 and graduates at the same raise. The staking pool is funded at creation and streams rewards over 60 days. See [Token staking](broken://pages/8d9522606ab45827258b83da515320486c78269b).

{% hint style="info" %}
With staking enabled, the Uniswap pool opens with a thinner 20% LP at a higher opening price — the same $9,000 of ETH is paired against 20% of the supply instead of 30%.
{% endhint %}

## Fees

RobinFun charges a symmetric **1% trade fee**, split evenly between the token creator and the protocol treasury, on every buy and sell — before and after graduation. See [Fees](broken://pages/4507dfe7eef9af897ddbef4be256c4a624431389).


---

# 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://robinfun.gitbook.io/robinfun-docs/tokenomics.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.