# Road Map \ **Phase 1: Planning, Community, and First Steps** * Project Launch: Start MaskNumber on the Solana Blockchain using Pump.fun to make it stealth launch. * Community Building: Grow a community on Telegram and Discord (coming soon) to share our private and safe ideas. * Start Beta Telegram Bot Testing: Test the Telegram bot with basic features and use feedback from users and the community to make it better. * Check Revenue Share: Look at the revenue share system to make sure the first payment to token holders goes well. **Phase 2: More Building and Quiet Launch** * Launch the Progress Dashboard: Create a dashboard where token holders can see the progress of number sales, token holders, and MaskNumber coin details, so users can check the bot’s status. * Build a dApp: Make a web app (dApp) on the website for users who don’t want to use Telegram, letting them buy numbers with USDT, USDC, or SOL. * Personal Dashboard: Add a personal dashboard for holders with 0.3% of tokens, so they can see their progress and revenue share payments. * Rebuild the Website: Update the website to include the dApp and dashboards for a better user experience. **Phase 3: Growing, Marketing, and Partnerships** * Growing: Keep working on the project, find more investors, and grow the community. * Marketing Push: Do more marketing to keep people interested and bring in new users. (detailed plans will be pushed out later) * Market Plans: Make plans to keep the market stable and growing. * Expand Services and Countries: Add more features, countries, and services to make buying numbers better. * Be Flexible: Change plans when needed to stay successful and important for a long time. --- # 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://masknumber.gitbook.io/masknumber-docs/road-map.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.