> For the complete documentation index, see [llms.txt](https://degen-games-2.gitbook.io/degen-games-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://degen-games-2.gitbook.io/degen-games-docs/how-the-game-works/creator-controls.md).

# Creator Controls

Once a coin is live, its creator controls almost nothing. That's the point.

Once a coin is live, the creator steps back from the controls. The rules are set at launch, and the contracts hold everyone to them, including the creator and Degen Games.

## Locked at launch

* **Supply:** 1,000,000,000. There's no mint function.
* **Pricing:** the curve's virtual reserve and graduation target.
* **Raise asset:** ETH, USDG or the stock chosen at launch.
* **Creator tax:** fixed, and it can never be raised.
* **Fee split:** the trading fee and how it's divided.
* **Snipe terms:** the window, starting rate and exempt wallets.
* **Liquidity:** burned at graduation. Nobody can reach it.

## What a creator can still change

### 1. Where the fees go

The current fee recipient can hand the fee stream to a different wallet.

* It takes effect **immediately**.
* It moves **future** earnings only. Balances already credited stay with the old wallet, so claim first.
* If the coin has buybacks on, the buyback vest moves with it.
* It's one-way: the old wallet can't take it back.

### 2. Whether to buy back

A creator can switch [creator buybacks](/degen-games-docs/how-the-game-works/fees.md#optional-creator-buybacks) on or off. Only the creator can turn them **on**, because they're paid for out of the creator's share. The protocol can turn them **off**, but never on.

{% hint style="info" %}
If a coin sends its fees to [holder rewards](/degen-games-docs/how-the-game-works/holder-rewards.md), the rewards vault is the fee recipient **permanently**. The vault never hands the fee stream on.
{% endhint %}

## What nobody can do

Every coin's ownership is burned to **`0x…dEaD`** in the deploy transaction, so there's no owner key for anyone to use. There's no function, for the creator or for Degen Games, that can:

* mint new tokens,
* freeze or blacklist a wallet,
* add or raise a tax after launch,
* change the raise asset or the curve,
* withdraw the burned liquidity.

## Lost wallets and abandoned coins

Sometimes a creator vanishes or loses access to their wallet while the community keeps going. For that case there's a **slow, public recovery path** for the fee stream:

{% stepper %}
{% step %}

### A new recipient is proposed

Degen Games proposes a new fee recipient, usually a wallet run by the active community. The proposal is on-chain and public. It names the new wallet and the time it takes effect.
{% endstep %}

{% step %}

### A 3-day waiting period

Nothing happens for **3 days**. Holders see the change coming and have time to react. Degen Games can cancel the proposal during the wait.
{% endstep %}

{% step %}

### A 3-day window to execute

After the wait, **anyone** can execute the change. If nobody does within the next **3 days**, the proposal expires.
{% endstep %}
{% endstepper %}

A takeover changes **who gets paid**, nothing else. The supply, pricing, raise asset, tax and liquidity stay exactly as they were.

A creator moving their fees to another wallet during the waiting period does **not** cancel the proposal. That's deliberate: otherwise someone who had stolen a creator's wallet could dodge the recovery that was set up because it was stolen.

{% hint style="info" %}
Anyone can read a pending change with `pendingCreatorFeeRecipient(token)` on the launch factory. It returns the proposed wallet and the times it becomes valid and expires.
{% 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://degen-games-2.gitbook.io/degen-games-docs/how-the-game-works/creator-controls.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.