> 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/community-takeover.md).

# community takeover

A token's **creator fee** (the 0.5% creator share) is normally paid to the fee address chosen at launch. If the original creator goes inactive, a **Community Takeover (CTO)** lets an active community redirect that creator fee to a new steward — through a deliberately gated, transparent process.

## How it works

1. **Request** — anyone can submit a CTO request from the token's page, providing the **new fee-destination address** and contact links (Telegram, X). The request is a gasless wallet signature; it costs nothing.
2. **Manual review** — every request is **reviewed manually by the RobinFun team**. Submitting a request grants no rights and changes nothing on its own.
3. **Approval** — only on **explicit team approval** is the creator fee reassigned to the new wallet on-chain. The reassignment is an owner-restricted contract action, so no one else can trigger it.

## What a CTO does and doesn't change

|                    |                                                                         |
| ------------------ | ----------------------------------------------------------------------- |
| ✅ Redirects        | The **0.5% creator fee**, to the approved wallet, from approval onward. |
| ❌ Doesn't touch    | The protocol treasury's 0.5% share.                                     |
| ❌ Doesn't change   | The token's supply, price, curve, or liquidity.                         |
| ❌ Doesn't transfer | Ownership of the token itself — the token stays exactly as it was.      |

## Eligibility

CTO is available for tokens launched through the RobinFun factory. A small set of early legacy tokens have immutable fee settings and keep their original arrangement.

## Why it's gated

Requiring manual review plus an explicit on-chain approval prevents abuse: no one can quietly capture another creator's fee stream by spamming requests. The gate keeps the process fair and auditable — every approval is a public on-chain transaction.


---

# 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/community-takeover.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.