> For the complete documentation index, see [llms.txt](https://bloxhood.gitbook.io/bloxhood-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bloxhood.gitbook.io/bloxhood-docs/roadmap.md). # Roadmap ### Phase 1 • Foundation * Launch $BloxHood & Build the core community * Token Generation Event (TGE) * Launch strategic community airdrops to selected Robinhood Chain ecosystem communities *** ### Phase 2 • Studio Formation * Identify promising Roblox experiences * Begin funding and acquisition discussions with developers * Complete the first game acquisition or partnership * Publish development updates and performance reports *** ### Phase 3 • Portfolio Expansion * Expand the BloxHood game portfolio * Support existing projects with development and marketing * Launch additional Roblox experiences * Grow recurring Robux revenue across the studio *** ### Phase 4 • Ecosystem * Introduce staking for long term supporters * Implement community governance features * Explore recurring revenue sharing mechanisms * Continue token buybacks using a portion of studio generated revenue * Scale the studio through additional acquisitions and strategic partnerships --- # 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://bloxhood.gitbook.io/bloxhood-docs/roadmap.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.