> For the complete documentation index, see [llms.txt](https://docs.storm.tg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storm.tg/storm-token-overview/launch_plan.md). # Launch Plan (Archive) Although all four phases of the $STORM launch are now complete, each played a key role in shaping the active Storm Trade community. The launch was executed in four stages, each offering unique goals and opportunities for users to participate and earn rewards. ## 📍 Phase 1: Public Testnet Users tested STORM on the TON mainnet without risk, completed tasks, and earned points for the airdrop. Active participants were rewarded and helped prepare the protocol for release. > ⚠️ The testnet phase is over, but the storm is just getting started! *** ## 📍 Phase 2: Public Beta During the open beta testing, users traded and provided liquidity to the SLP, earning RP points that could be exchanged for tokens after the TGE. *** ## 📍 Phase 3: Market Makers NFT A collection of 5,555 unique NFTs granted whitelist access before the TGE. Users could earn these NFTs through tournaments, referrals, community involvement, or by purchasing them on Getgems. > 🃏 The [Market Makers NFT](https://getgems.io/market-makers) collection is available on GetGems. *** ## 📍 Phase 4: STORM Token Generation Event (TGE) A fair and open token launch was held across multiple Launchpad platforms. Market Makers NFT holders used their whitelist access to purchase tokens before public trading began. --- # 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://docs.storm.tg/storm-token-overview/launch_plan.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.