> For the complete documentation index, see [llms.txt](https://info-69.gitbook.io/dogecoffee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info-69.gitbook.io/dogecoffee/project/roadmap.md). # 🏁 Roadmap ## Phase 1: * Project vision & ideas * Website launch * Social Media launch * 5000 telegram members * Contract development on BSC * Contract development on ETH * Ownership renounced * Audit & KYC by SolidProof * Unicrypt ILO Presale launch ## Phase 2: * Listing on CG/CMC * Marketing plan execution * 25,000 telegram members * 25,000 holders * Website redesign * Partnership with small coffee brands * DogeCoffee Swap launch * DogeCoffee NFTs launch ## Phase 3: * 100,000 holders * 100,000 telegram members * DogeCoffee Full app launch * Massive marketing push * Listings on major CEX * Partnership with top coffee brands * DogeCoffee dApps launch For coffee brands * DogeCoffee Metaverse launch * DogeCoffee charity & donation --- # 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://info-69.gitbook.io/dogecoffee/project/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.