> For the complete documentation index, see [llms.txt](https://rootwood.gitbook.io/rootwood-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rootwood.gitbook.io/rootwood-docs/lifecycle-three-phases.md). # Lifecycle: three phases #### Phase 1 · Mint Up to **999 Rootlings** are minted for ETH at a fixed price of **0.00067 ETH**. Proceeds belong to the creator and are never auto-refundable — this is a clean primary sale. ``` ETH ──mint──▶ Rootling (ERC-721, whole) ``` #### Phase 2 · Launch The creator launches ROOT — a fixed supply of **999,000** — and splits it across three buckets: the swap allocation, the trading pool, and the team. A chosen slice of the mint ETH is seeded into the pool as depth; everything else stays withdrawable. ``` ROOT (999,000) ──split──▶ 50% swap · 35% pool · 15% team ``` #### Phase 3 · Live Every holder can now swap their Rootling into **500 ROOT** — the NFT burns, the tokens release, one way and irreversible. ROOT trades against ETH on the constant-product curve, buy and sell, forever. ``` Rootling ──swap──▶ 500 ROOT (one-way, NFT burned) ROOT ⇄ ETH on the curve (buy climbs, sell descends) ``` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rootwood.gitbook.io/rootwood-docs/lifecycle-three-phases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.