> 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/player-1-press-start/collect-creator-fees.md).

# Collect Creator Fees

Your coin earns on every trade, on the curve and after graduation. Here's how to collect.

Launch a coin and you earn from every trade on it, for as long as it trades. That covers the bonding curve **and** the Uniswap pool after graduation.

## What you earn

| Source                              | Your share                                                    |
| ----------------------------------- | ------------------------------------------------------------- |
| Trading fee (1% of every trade)     | **0.7%** of every trade. The other 0.3% goes to the platform. |
| Creator tax (0–10%, if you set one) | **100%** of it                                                |

Example: a coin with no creator tax does 10 ETH of volume. The trading fee is 0.1 ETH. You earn **0.07 ETH**, and 0.03 ETH goes to the platform, which uses it for the [buyback and burn](/degen-games-docs/usdmanyu/buyback-and-burn.md).

If you turned on [holder rewards](/degen-games-docs/how-the-game-works/holder-rewards.md), **all** of it goes to your holders instead of you: the 0.7% share and any creator tax.

## Paid in the raise asset

You're paid in whatever your coin raises in, with no conversion.

* ETH coins pay **ETH**.
* USDG coins pay **USDG**.
* Stock coins pay **that stock token**, for example AAPL.

If you've launched coins with different raise assets, you'll have a separate balance for each one.

## Claim

{% stepper %}
{% step %}

### Open My Profile

Connect the wallet that is the coin's **fee recipient**, then open **MY PROFILE** from the sidebar.
{% endstep %}

{% step %}

### Go to Creator Fees

**CLAIMABLE CREATOR FEES** shows your share of trade fees across every coin you launched, both on the curve and graduated.
{% endstep %}

{% step %}

### Press CLAIM

Confirm in your wallet. One claim collects everything owed in that asset.
{% endstep %}
{% endstepper %}

## How fees reach you

Fees are **pulled, never pushed**. That's deliberate: if payouts were pushed automatically, one wallet that couldn't receive a transfer could jam payouts for everyone else.

1. **Earned.** Every trade sets fees aside. On the curve they sit in the coin's curve. After graduation they sit in the Uniswap hook.
2. **Swept.** Fees are periodically swept into the **fee escrow**, a shared contract that keeps a balance for every recipient.
3. **Claimed.** You withdraw your escrow balance whenever you like. There's no deadline.

{% hint style="info" %}
A trade you just saw might not show in your claimable balance yet. It appears after the next sweep.
{% endhint %}

## Handing off your fee stream

The current fee recipient can pass the fee stream to another wallet at any time. It takes effect immediately, but only for **future** earnings. Anything already credited stays with the old wallet, so **claim first**.

{% hint style="warning" %}
Once you hand the fee stream to another wallet, you can't take it back. Only the new recipient can move it again.
{% endhint %}

See [Creator Controls](/degen-games-docs/how-the-game-works/creator-controls.md) for the full list of what a creator can and can't change.


---

# 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 dynamically 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/player-1-press-start/collect-creator-fees.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 `build a script that syncs our docs to a CMS` 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.