> 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/risks.md). # Risks Read this before you launch or trade a token on Navo. > Navo is not live yet. The contracts are not deployed and not audited. Contract addresses and audit reports will be published here before launch. This documentation describes the planned product. ## Before you take part * **Prices can go to zero.** New tokens are very volatile. Only use money you can afford to lose. * **Names can be copied.** Anyone will be able to launch a token with a name or symbol that another token uses. Always check the token address. * **Graduation is not a quality signal.** It will mean the bonding curve has sold out and the token's graduation pool will be deployed on Hybra. It will not establish token quality or future returns. * **Other venues can have other rules.** A token may also trade on other exchanges, where Navo's fees and rules will not apply. * **Smart contracts can fail.** Contracts can have bugs, even after an audit. * **Transactions are final.** On-chain transactions cannot be undone. Review the quote and wallet confirmation before trading. ## Stay safe * Use only links from official Navo channels. * Check the URL before you connect your wallet. * Check the contract address before you approve or trade. Nothing in this documentation is financial advice. --- # 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/risks.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.