> 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/overview/chainlink-x-manyu.md).

# Chainlink × Manyu

Degen Games is a collaboration project between Chainlink and Manyu.

Degen Games is a **collaboration project between Chainlink and Manyu**. Manyu brings the community and the launchpad-supported token. Chainlink works on development and on the cross-chain integrations that let one arcade run on many chains.

## Manyu

[Manyu (@RealManyu)](https://x.com/RealManyu) is the social-media-famous Shiba Inu with a huge following across TikTok, Instagram and YouTube. **$MANYU** is her community token: 1 quadrillion supply, liquidity burned, contract renounced, 0% buy and sell tax.

Manyu's partners include **Chainlink** and **HTX**, one of the world's largest crypto exchanges, where $MANYU is listed.

In Degen Games, $MANYU is the **launchpad-supported token**. The arcade doesn't mint a new one. Instead, the platform's share of trading fees on every chain goes to buying $MANYU and burning it.

* [The MANYU Token](/degen-games-docs/usdmanyu/manyu-token.md)
* [Buyback & Burn](/degen-games-docs/usdmanyu/buyback-and-burn.md)

## Chainlink

[Chainlink](https://chain.link) provides decentralized oracle and cross-chain infrastructure used across DeFi, and it's a recognized partner of Manyu.

In September 2025, Chainlink announced that MANYU had become a **Cross-Chain Token (CCT)**. With **Chainlink CCIP**, holders can transfer MANYU between BNB Chain and Ethereum:

{% embed url="<https://x.com/chainlink/status/1970699713729994918>" %}

{% embed url="<https://x.com/chainlink/status/1970700363314639071>" %}

In Degen Games, Chainlink is involved in two areas:

* **Development.** Chainlink collaborates on building the platform.
* **Cross-chain integrations.** Degen Games runs on many chains but supports one token. Connecting those chains, so a coin can launch on any of them and the revenue from all of them reaches a single buyback, is cross-chain work.

## How the two fit together

{% stepper %}
{% step %}

### Coins launch on many chains

Players launch and trade coins on Robinhood Chain and BNB Chain today, with Ethereum and other EVM chains next.
{% endstep %}

{% step %}

### Every trade pays the trading fee

Each trade pays a 1% trading fee: 0.7% to the coin's creator and 0.3% to the platform. The platform's share is collected on the chain where the trade happened.
{% endstep %}

{% step %}

### Revenue is bridged automatically

That revenue is bridged automatically, whichever chain earned it. Nobody has to move it by hand.
{% endstep %}

{% step %}

### $MANYU is bought and burned

The bridged revenue buys $MANYU on the market and sends it to the burn address. That permanently reduces the supply.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Burning reduces supply. It does not guarantee any price for $MANYU.
{% 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/overview/chainlink-x-manyu.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.