> 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/multi-chain/supported-chains.md).

# Supported Chains

One arcade, many chains. Robinhood Chain and BNB Chain are live, with more EVM chains next.

**One arcade, many chains.** Degen Games runs the same contracts and the same rules on every EVM chain it supports. Switch chains with the network selector in the top bar. Your wallet stays the same.

## Rollout

| Chain                                                                   | Chain ID | Gas token | Status                        |
| ----------------------------------------------------------------------- | -------- | --------- | ----------------------------- |
| [**Robinhood Chain**](/degen-games-docs/multi-chain/robinhood-chain.md) | 4663     | ETH       | 🟢 **Live**, the launch chain |
| [**BNB Chain**](/degen-games-docs/multi-chain/bnb-chain.md)             | 56       | BNB       | 🟢 **Live**                   |
| **Ethereum**                                                            | 1        | ETH       | 🟡 Next                       |
| **Other EVM chains**                                                    | —        | —         | ⚪ Planned                     |

New chains are announced on [@DegenGamesVIP](https://x.com/DegenGamesVIP) and added to [Contracts](/degen-games-docs/developers/contracts.md) as they go live.

## The same game everywhere

On every chain:

* A **1,000,000,000** fixed supply per coin, launched on a **bonding curve**.
* **Automatic graduation** into the chain's DEX, with the **LP burned**.
* The same **1% trading fee** (0.3% platform, 0.7% creator) and optional **0–10% creator tax**.
* **Snipe protection** in the first seconds of every launch.
* **Holder rewards** and **automatic contract verification**.

## What's sized per chain

Some numbers depend on the chain's native token and its markets, so they're set per chain and stored on-chain:

* The **launch fee**: 0.0005 ETH on Robinhood Chain, 0.0015 BNB on BNB Chain.
* The **graduation target** and virtual reserve for each raise asset.
* The list of approved **raise assets**. Every chain starts with its own gas token — ETH graduating at 4.2 on Robinhood Chain, BNB graduating at 14.5 on BNB Chain — plus that chain's stablecoins and tokenized stocks.

Read them from each chain's launch factory. See [Reading State](/degen-games-docs/developers/reading-state.md).

## Revenue from every chain meets in one place

Coins trade on many chains, but the launchpad supports one token. The platform's 0.3% share of trades on every chain is bridged automatically and used to buy back and burn it. See [Buyback & Burn](/degen-games-docs/usdmanyu/buyback-and-burn.md).

{% hint style="info" %}
A coin lives on the chain it was launched on. Launching on Robinhood Chain doesn't create copies on other chains. Coins on different chains are separate tokens, even if they share a name.
{% 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/multi-chain/supported-chains.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.