> 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/help/faq.md). # FAQ Short answers to common questions. ## Launchpad ### What do I trade with? HYPE. Tokens on Navo will be priced and traded in HYPE, and gas on Elysium will be paid in HYPE. ### What does graduation mean? The bonding curve will have sold all its tokens. The token will move into a liquidity pool on **Hybra**. All liquidity pools created through Navo's graduation process will be deployed on Hybra, with liquidity permanently locked. Graduation will not be a signal of token quality. ### What is the snipe tax? An extra tax on buys immediately after a launch. It is designed to make buying ahead of other users more expensive for bots, and will drop to zero over a short window after launch. See [Snipe protection](https://navofamily.gitbook.io/navo-docs/launchpad/trade#snipe-protection). ### Can anyone remove the liquidity of a graduated token? No. Under the planned design, liquidity in Navo's graduation pools on Hybra will be locked permanently. The creator, Navo and other users will not be able to remove it. ### Why do LPs earn no fees in Navo pools? The planned Navo pool fee model will preserve the creator's 50% share without dilution from additional LPs. Trading-fee revenue will be split 50% to the creator, 38% to the Navo protocol, 10% to the Rebound Cash pool, 1% to buy HYPE for the Hyperliquid Assistance Fund, and 1% to buy back and burn KNTQ. These are shares of fee revenue; the total trading fee will be 1% of trade value. Of every 100 in fee revenue, the protocol will receive 38, use 20 to buy back and burn NAVO, and retain 18. See [Fees](https://navofamily.gitbook.io/navo-docs/launchpad/fees). ### In which asset are creators paid? HYPE. If **Buyback & lock** is on, the creator will also receive part of the bought-back tokens, in the token itself. See [Creator earnings](https://navofamily.gitbook.io/navo-docs/launchpad/creator-earnings). ### Can the creator's share buy back the token? Yes. With **Buyback & lock**, half of the creator's share will buy the token. Navo will lock the bought tokens and will not burn them. They will unlock over 5 years. See [Buyback and lock](https://navofamily.gitbook.io/navo-docs/launchpad/creator-earnings#buyback-and-lock). ## Safety ### Is Navo audited? Not yet. Navo is not live. Audit reports and contract addresses will be published before launch. See [Risks](https://navofamily.gitbook.io/navo-docs/help/risks). --- # 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/help/faq.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.