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

# robinfun staking

Beyond each launchpad token's own staking, the main **ROBINFUN** token has a dedicated **revenue-share pool**: stake ROBINFUN and earn **native ETH**, funded by the protocol's fee revenue.

This is different from [per-token staking](broken://pages/6b982ca3e22206031f505301c91a19a47602a511) — here you stake ROBINFUN and the reward is **ETH**, not a token.

## How rewards are funded

The protocol treasury sends a share of collected fees (in ETH) to the staking pool and arms a **30-day reward stream**. The ETH then drips out continuously over the stream and is split **pro-rata by position weight** — nothing pays out instantly, and nothing depends on new stakers joining.

| Property       | Detail                                                                                                 |
| -------------- | ------------------------------------------------------------------------------------------------------ |
| Reward asset   | **Native ETH** on Robinhood Chain — the same asset fees are collected in. No wrapped token, no bridge. |
| Funding source | Protocol fee revenue, sent by the treasury.                                                            |
| Stream length  | 30 days per funding round. Rewards accrue every second while a stream is active.                       |
| Accrual        | Pro-rata to `amount × lock days` across all open positions.                                            |

## Locks and weight

| Rule          | Detail                                                                                       |
| ------------- | -------------------------------------------------------------------------------------------- |
| Lock options  | **14, 30, 45, or 60 days** — you pick per position.                                          |
| Reward weight | `amount × lock days`. A 60-day lock earns ≈ **4.3×** the per-ROBINFUN rate of a 14-day lock. |
| Positions     | A wallet can hold up to **100 open positions**, each independent.                            |
| Claiming      | You can **claim ETH** or **withdraw principal + ETH** once a position's lock expires.        |
| Principal     | Your staked ROBINFUN always comes back in full — rewards affect only the ETH side.           |

## How to stake

1. Open the **Staking** page in the app.
2. Choose a **lock period** (14 / 30 / 45 / 60 days) and an **amount** of ROBINFUN.
3. Approve, then confirm the stake.
4. Accrue ETH continuously; **claim** or **unstake** after your lock expires.

{% hint style="warning" %}

## Keep in mind

* Rewards accrue **only while the pool has an active reward stream**. Before the pool's first stream is armed you can stake, but you accrue nothing until it starts. Once a stream **ends**, new stakes are rejected until the treasury arms the next funding round — existing positions are unaffected and can still claim and withdraw after unlock.
* A 30-day stream is how a batch of rewards is distributed — it is **not a waiting period**. You accrue continuously and can claim as soon as your own lock expires.
* If an ETH payout to your address ever fails (for example, a contract wallet that rejects ETH), your principal still returns and the ETH is credited to you inside the pool, claimable at any time.
* The staking pool is a standalone contract with no owner and no admin functions — its rules can't be changed after deployment. See [Contract addresses](broken://pages/9900e8f3df757cc7b9261705ec25681831aae6e0).
  {% 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://robinfun.gitbook.io/robinfun-docs/robinfun-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.