> For the complete documentation index, see [llms.txt](https://o2dao.gitbook.io/o2-dao-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://o2dao.gitbook.io/o2-dao-documentation/future/roadmap.md). # Roadmap #### What can we expect from O2 DAO in the future? O2 DAO's long term goal is to bring the wealth creation to the next level for all of our users. If OHM model is successful, then we will be at least twice successful as OHM since we are backed by OHM. Our growth would be exponentially better than OHM. O2 will constantly evolve and improve to satisfy our community and provide new solutions for all DeFi users across the world. #### V1 * Liquidity Bootstrap **V2** * OHM Hub * Acquire staking and governance tokens of prominent OHM forks * Diversify our treasury which improves overall returns and and stability * "OHM ETF" * Governance * Vote delegation (WIP) * Partnership * Seek partnership with OlympusDAO and become one of the official ways to encourage cross-chain gOHM. #### #### --- # 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://o2dao.gitbook.io/o2-dao-documentation/future/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.