# RoadMap . *** #### 🧱 Phase 01: **Foundation Blueprint** **Q1 2025** * Strategic documentation and planning * Initial funding round to support early-stage growth * Defining technical architecture and product requirements * Team expansion and operational setup > This phase laid the groundwork for what LunarBet will become — a world-class crypto iGaming platform powered by $LUNR. *** #### 🔥 Phase 02: **The Awakening** **Q2 2025** * MVP (Minimum Viable Product) development begins * Securing key advisors and strategic partners * Initial community building and internal product testing > With development underway, we began shaping the core experience and aligning with advisors who share our vision. *** #### 🚀 Phase 03: **Fires of Momentum** **Q2 2025** * Private token sale to strategic investors * Public token sale and community onboarding * Aggressive marketing rollout and brand awareness campaigns * Gambling license application submitted in **Anjouan (Comoros)** * **Beta Platform** > This phase marks the transition from build to scale — fueling growth, community engagement, and regulatory alignment. *** #### 🌕 Phase 04: **Rise of the Engines** **Q3 2025** * **Full platform launch** with core casino games * **$LUNR token launch** and **DEX listing** * Initial **CEX listing** for wider token accessibility * Expanded community rewards, leaderboard systems, and early VIP programs > We go live. The LunarBet ecosystem is activated, and players around the world can begin to experience the thrill of the next-gen crypto casino. --- # Agent Instructions: 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: ``` GET https://docs.lunarbet.io/roadmap.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.