> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/what-is-fyuz.md).

# ✨ What is Fyuz?

<div align="center"><img src="https://pbs.twimg.com/profile_images/2075862034751598592/6wPqjMaF_400x400.jpg" alt="Fyuz" width="160"></div>

⚡ **Two Icons Enter. One Market Leaves.**

**Fyuz** is a token launchpad on **BNB Smart Chain** built around one cultural mechanic: **fusion**. You pick two icons — personalities, memes, narratives, communities — and Fyuz's AI fuses them into a single character. That character becomes a token, launched instantly on a bonding curve. 🧬🚀

{% hint style="info" %}
📈 Every Fyuz token starts on a **bonding curve** that sets the price automatically. When a token reaches a **$30,000 market cap**, it graduates: liquidity is deployed to **PancakeSwap** and trading continues in the open market.
{% endhint %}

### 🔄 The lifecycle of a Fyuz token

1. **🧬 Fuse & launch** — name two icons, the AI generates the fused character image, and the token deploys with a fixed supply of **1,000,000,000**. Launching is free — you only pay gas.
2. **📈 Trade on the curve** — a constant-product bonding curve prices every buy and sell automatically. No order book, no liquidity providers, no presale: everyone trades against the same curve from the first block.
3. **🎓 Graduate** — when the token reaches a **$30,000 market cap**, the curve closes. Its BNB and remaining tokens are deployed as liquidity on **PancakeSwap**, the LP is locked forever, and leftover tokens are burned.

### 💡 What makes Fyuz different

|                                |                                                                                                                       |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
| 🧬 **Fusion launches**         | Name two icons — Fyuz's AI fuses them into a single character that becomes the token's identity.                      |
| ⚖️ **Fair by construction**    | Fixed 1B supply, no team allocation, no presale. Everyone buys on the same curve.                                     |
| 💸 **Aligned fees**            | A flat 1% trade fee split three ways: 0.5% platform treasury, 0.3% community leaderboard rewards, 0.2% token creator. |
| 📊 **A full trading terminal** | Discovery screener, portfolio PnL, wallet tracker, token analytics and live streaming — built in.                     |
| 🏆 **Rewards that compound**   | Points for trading, launching and referring, with seasons, tiers and an airdrop allocation tracker.                   |
| 🔴 **Live culture**            | Creators stream live on their token pages; every trade feeds the activity ticker and the King of the Hill race.       |

{% hint style="success" %}
🚀 New here? Start with [Getting Started](/getting-started.md) — you can be trading in under five minutes.
{% endhint %}

### 🔗 Links

* 🌐 Website: [fyuz.fun](https://fyuz.fun)
* 🐦 X / Twitter: [@fyuzfun](https://x.com/fyuzfun)


---

# 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://docs.fyuz.fun/what-is-fyuz.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.
