> 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/usdmanyu/buyback-and-burn.md).

# Buyback & Burn

Platform revenue from every chain is bridged automatically, used to buy $MANYU, and burned. Every trade in the arcade feeds the burn.

**Every trade feeds the burn.** Degen Games uses its platform revenue to buy **$MANYU** on the market and burn it. It doesn't matter which chain the revenue was earned on.

## The flow

{% stepper %}
{% step %}

### Trades pay the trading fee

Every trade on every coin pays a **1% trading fee**, on the bonding curve and after graduation. The creator earns 0.7% and the platform keeps **0.3%** of all volume in the arcade.
{% endstep %}

{% step %}

### Revenue is collected on each chain

The platform's share is collected on the chain where the trade happened: Robinhood Chain today, then BNB Chain, Ethereum, Base and more.
{% endstep %}

{% step %}

### It's bridged automatically

Revenue from every chain is bridged automatically. There's no manual step, and no chain is left out.
{% endstep %}

{% step %}

### $MANYU is bought and burned

The revenue buys $MANYU on the open market, and the $MANYU is sent to the burn address:

`0x000000000000000000000000000000000000dEaD`
{% endstep %}
{% endstepper %}

## By the numbers

| Arcade volume | Trading fees (1%) | Platform share, used for the $MANYU buyback (0.3%) |
| ------------: | ----------------: | -------------------------------------------------: |
|       100 ETH |             1 ETH |                                            0.3 ETH |
|     1,000 ETH |            10 ETH |                                              3 ETH |
|    10,000 ETH |           100 ETH |                                             30 ETH |

The same applies to coins that raise in USDG or tokenized stocks. The platform's share is collected in whatever asset the coin trades in.

## Deflationary by design

$MANYU has a fixed supply of 1 quadrillion and no mint function. Every burn permanently removes tokens from circulation, so the more the arcade is played, on any chain, the smaller the circulating supply of $MANYU gets.

## Verify it

* **Burns:** every burn is a $MANYU transfer to `0x…dEaD` on Ethereum. Check the burn address's MANYU balance on [Etherscan](https://etherscan.io/token/0x95AF4aF910c28E8EcE4512BFE46F1F33687424ce?a=0x000000000000000000000000000000000000dEaD).
* **Revenue:** the platform's fee recipient on each chain is public. Read it with `getLaunchFeePolicy(token).protocolFeeRecipient` on the launch factory. See [Contracts](/degen-games-docs/developers/contracts.md).
* **The split:** the platform's 0.3% (30% of the 1% trading fee) is stored on-chain for every coin. Read it with `getLaunchFeePolicy(token)` on the launch factory.

{% hint style="warning" %}
Burning reduces supply. It doesn't guarantee any price for $MANYU, and nothing here is financial advice.
{% 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 dynamically by asking a question.

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

```
GET https://degen-games-2.gitbook.io/degen-games-docs/usdmanyu/buyback-and-burn.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.