# Community Takeover

## Community Takeover (CTO) Process

If a creator has abandoned a token, the community has the opportunity to step in and take over the project's **reward pool** to ensure its continued growth and development. This process allows committed community members to keep a project alive and properly managed.

<figure><img src="/files/ySdoCdCoTDoaE30BExBW" alt="" width="375"><figcaption><p>CTO manager card</p></figcaption></figure>

### How It Works

1. **Application Submission**
   * A community member or group can apply to become the new **CTO (Community Takeover Team)** through our platform.
   * The application requires a **199 USDC fee**, which covers verification and processing.
2. **Review & Verification**
   * Each CTO application is **manually reviewed** by our team.
   * We verify that the original creator has **abandoned the project**, ensuring a legitimate takeover request.
   * The proposed CTO team is also vetted for legitimacy and ability to manage the project.
   * This process is rigorous and typically completed **within 48 hours**.
3. **Approval & Rewards Reallocation**
   * If the CTO application is **approved**, the project's **reward pool** is transferred to the **new wallet** designated by the CTO team.
   * The **original creator loses all future reward claims**, preventing misuse.
   * The new CTO team gains access to rewards, ensuring incentives to manage and grow the project.
4. **CTO Identification & Manager Card**
   * Once a token has been taken over by a CTO team, it will be marked as a **CTO Token** on the platform.
   * A **CTO Manager Card** will be displayed **under the chart on the token’s page**, showing the new wallet where the **creator rewards** are now allocated.
   * This ensures **transparency** and allows the community to see who is managing the project.
5. **Fee Allocation**
   * **100% of the application fee** is distributed to the **Gochu staking rewards pool**.

This process ensures abandoned tokens have a **chance to survive and thrive**, benefiting both the community and Gochu holders.

[Apply for a community takeover (CTO)](https://forms.gle/EEqnAxCfWabbpmRM6)

***

### Terms & Conditions: CTO Takeover

1. **Eligibility & Application**
   * Any community member or group can apply for a CTO takeover.
   * The application requires a **199 USDC non-refundable fee**.
2. **Verification Process**
   * All applications undergo a strict **manual review** to confirm the project’s abandonment.
   * The verification process is completed within **48 hours**, but timing may vary.
3. **Final Decision & Transfers**
   * If approved, the new CTO team receives **full access to the project's reward pool**.
   * The **original creator is permanently removed from future claims**.
4. **Fee Distribution**
   * **The full application fee** is added to the **Gochu staking rewards pool**.
5. **Liability & Disputes**
   * The platform is **not liable** for any project mismanagement by the new CTO team.
   * All takeover decisions are **final**, and there is no appeals process.

By applying for a CTO position, users agree to these **Terms & Conditions** and acknowledge the **finality of decisions** made by the verification team.

{% hint style="info" %}
To apply for a CTO please fill in the form and complete payment [here](https://forms.gle/EEqnAxCfWabbpmRM6).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gochu-fun.gitbook.io/gochufun/additional/community-takeover.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.