> 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/fees.md). # Fees What traders will pay on Navo, and where every fee will go. ## What traders pay | When | Fee | | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Trade on the bonding curve | **1% of trade value** | | Swap in a graduated Navo pool on Hybra | **1% of trade value** | | Buy immediately after launch | Snipe tax, on top of the standard trading fee. The starting rate and duration will be announced before launch. See [Snipe protection](https://navofamily.gitbook.io/navo-docs/launchpad/trade#snipe-protection). | Gas is separate from the trading fee. Review the quote and wallet confirmation before trading. ## Where every fee goes Navo's trading fee revenue will be distributed as follows: ``` Trading fee revenue ├── 50% ──▶ Token creator ├── 38% ──▶ Navo protocol ├── 10% ──▶ Rebound Cash pool ├── 1% ──▶ Buy HYPE and send it to the Hyperliquid Assistance Fund └── 1% ──▶ Buy back KNTQ and burn the purchased tokens ``` | Share of fee revenue | Goes to | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **50%** | The token's creator, paid in HYPE. The creator will be able to use part of it to buy back their token. See [Creator earnings](https://navofamily.gitbook.io/navo-docs/launchpad/creator-earnings). | | **38%** | Navo protocol revenue. Of every 100 in total fee revenue, 20 funds NAVO buybacks and burns and 18 is retained by the protocol. | | **10%** | The Rebound Cash pool, funding rewards for eligible trading losses. | | **1%** | Buying HYPE and sending it to the Hyperliquid Assistance Fund. | | **1%** | Buying back KNTQ and burning the purchased tokens. | The same split will apply on the bonding curve and in graduated Navo pools on Hybra. These percentages divide **fee revenue**; they are not additional percentages of trade value. For example, a 1,000 USDC-equivalent trade at the standard 1% fee will produce 10 USDC-equivalent in fee revenue: 5 for the creator, 3.80 for the protocol, 1 for the Rebound Cash pool, 0.10 for the HYPE purchase and 0.10 for the KNTQ buyback and burn. Of the protocol’s 3.80, 2 will fund NAVO buybacks and burns and 1.80 will be retained. ## Navo buybacks Navo will use **20% of total trading-fee revenue, drawn from its 38% protocol share, to buy back NAVO**. The protocol will retain the other 18% of total fee revenue. The buyback budget will equal **0.20% of trade value** at the standard 1% trading fee. **All NAVO purchased through these protocol buybacks will be burned.** ## Liquidity providers earn no fees **All graduated liquidity pools will be deployed on Hybra.** In these Navo pools, the whole 1% trading fee will go to the split above. Liquidity providers will earn none of it. This rule will be built into the pool and will not be changeable by Navo or anyone else. This describes Navo's graduated pools. Fees on independently created third-party pools may differ. --- # 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/fees.md?ask=&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.