> For the complete documentation index, see [llms.txt](https://docs.nuon.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuon.fi/token-release-stages.md). # Token Release Stages MaxCap token release happens in stages after the Guarded Launch ## Token Release Documentation ### Token Lifecycle Events: TGE, Token Sale, and DEX Listing To avoid confusion, the Nuon documentation defines the terminology we use to describe key lifecycle events related to the MaxCap token. #### TGE (Token Generation Event) * **Definition**: The moment when MaxCap tokens are technically deployed to the blockchain. * **Timing**: Internally complete once the token contract is deployed. * **Access**: Users typically do not receive or interact with tokens at this stage. #### Token Sale * **Definition**: The event where users can purchase MaxCap tokens via public launchpads, a Dutch auction, or private sale rounds. * **Access**: Users may commit capital during the sale but might not receive tokens immediately. #### DEX Listing (Public Launch) * **Definition**: The point at which MaxCap becomes publicly tradable on decentralized exchanges (DEXs). * **Timing**: Occurs after the Token Sale concludes. * **Preferred Term**: Going forward, we'll use "DEX Listing" or "Public Launch" interchangeably when referring to tokens becoming accessible to the general public. --- # 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://docs.nuon.fi/token-release-stages.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.