> For the complete documentation index, see [llms.txt](https://navofamily.gitbook.io/navo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navofamily.gitbook.io/navo-docs/launchpad/launch-a-token.md).

# Launch a token

Launch your own token on Navo.

Navo is not live yet. The steps below describe the planned launch flow on Elysium.

## Before you start

* A wallet connected to Elysium.
* HYPE on Elysium for gas and the launch fee. The launch fee will be announced before launch.

## Steps

1. Open the **Create** page on Navo.
2. Fill in your token:
   * **Name** and **symbol**
   * **Description**: a short line about the token
   * **Image**
   * **Links**: X and Telegram (optional)
   * **Buyback & lock**, under **Advanced**: on by default. See [Buyback and lock](https://navofamily.gitbook.io/navo-docs/launchpad/creator-earnings#buyback-and-lock).
3. Click **Launch token** and confirm in your wallet.

Your token page will go live as soon as the transaction confirms. Share it. The token will be tradable right away.

## After launch

* Your earnings will start with the first trade. You will receive **50% of trading fee revenue** on your token. See [Creator earnings](https://navofamily.gitbook.io/navo-docs/launchpad/creator-earnings).
* The supply and the trading rules will be fixed at launch. Nobody will be able to change them later.
* If the token graduates, its liquidity pool will be deployed on **Hybra**. All graduated pools will be deployed on Hybra. See [How the launchpad works](https://navofamily.gitbook.io/navo-docs/launchpad/how-it-works).

> Token names are not unique. Someone else may launch a token with the same name as yours. Traders should check the token address, not only the name. Share your token page link so your community finds the right one.


---

# 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://navofamily.gitbook.io/navo-docs/launchpad/launch-a-token.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.