> For the complete documentation index, see [llms.txt](https://clio-defi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clio-defi.gitbook.io/docs/roadmap.md). # Roadmap Four phases. Phase I is complete; Phase II is active at the time of writing. ### Phase I — Foundation (Completed) * Brand and website launched * Whitepaper published * Security review preparation completed * Seed sale round closed * X and Telegram community established ### Phase II — Public Mainnet (Active) * Token Generation Event * Mainnet launch on BNB Smart Chain * Independent security review initiated * Initial liquidity bootstrapped on PancakeSwap V3 and Biswap * Core partner outreach (validator partners, lending venues) ### Phase III — Module Expansion (Upcoming) * Staking pools opened across the full schedule (7-day, 30-day, 90-day) * Dashboard v2: full timeline mode, multi-wallet aggregation, mobile-optimized * First centralized exchange listing * Lend module beta opens to all users ### Phase IV — The Long Form (Future) * DAO governance live; Treasury Reserve transitions from multi-sig to onchain governance * Cross-chain expansion to Ethereum and Arbitrum (Router contract redeployment, vault deployment per chain) * Lend module expands to cross-chain collateral markets * Ecosystem Fund deployments to partner protocols ### Phase Transitions We avoid quarter-boundary deadlines for phase transitions because they tend to produce two failure modes: rushed delivery near a deadline, or visible silence after one. Phase transitions are announced when each phase's milestones are independently complete. The most reliable tracker of progress is the project's quarterly transparency report, published in [Community & Governance](broken://pages/1a65c6cb6f8a086f38a54bccf40ebe1e0d8f9ba8). --- # 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://clio-defi.gitbook.io/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.