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

# token staking

When a creator **enables staking at launch**, 10% of the token's supply is set aside to reward holders who lock their tokens. This is per-token staking: you stake a launchpad token and earn **that same token**.

## How it's funded

Enabling staking changes the launch split to **70% curve / 20% LP / 10% staking** (see [Token economy](broken://pages/0d09cd7b47508c9c6d67561deb30ead6afef8f9e)). The 10% allocation funds the reward pool, which is created and funded **at launch** and streams rewards continuously over **60 days**.

Because the stream starts at creation, staking is open — and rewards accrue — **both before and after graduation**.

## Locks and weight

Staking is **locked** and **multi-position**:

| Rule          | Detail                                                                                                                                                  |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Lock options  | **14, 30, 45, or 60 days** — each staker picks per position.                                                                                            |
| Reward weight | `amount × lock days`. A 60-day lock earns ≈ **4.3×** the per-token rate of a 14-day lock.                                                               |
| Positions     | A wallet can hold up to **100 open positions**, each with its own amount, lock, and timer.                                                              |
| Withdrawals   | A position can only be withdrawn or claimed **after its own lock expires**.                                                                             |
| Stream window | Rewards stream for 60 days from launch. Once the stream ends, no new stakes are accepted; existing positions can still withdraw and claim after unlock. |

## How to stake

1. Open the token's page — the staking panel appears when the creator enabled staking.
2. Choose a **lock period** and an **amount**.
3. Approve the token, then confirm the stake.
4. After your lock expires, **claim** your rewards or **withdraw** your principal together with rewards.

## Rewards are paid in the token

For per-token staking, the reward asset is the **staked token itself**, drawn from the 10% staking allocation.

> **Note**: Looking to earn **ETH** instead? The main ROBINFUN token has a separate revenue-share pool that pays rewards in native ETH — see [ROBINFUN staking](broken://pages/af13b401f700eadc5b57c379336d99786fdf53ca).


---

# 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/token-staking.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.