> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/roadmap/omen-protocol-roadmap.md). # Omen Protocol Roadmap Explore the development roadmap of Omen Protocol, from its initial launch and utility development to multichain expansion and long-term ecosystem growth. OMEN Protocol is building a crypto intelligence platform that connects market research, AI-assisted analysis, and trading tools. ### Phase 1 — Foundation & Launch * Build the official website and project presence. * Establish the OMEN community and communication channels. * Launch $OMEN through PONS Launchpad. ### Phase 2 — OMEN Utility * Develop and launch OMEN Utility. * Introduce Robinhood Chain support. * Integrate token swap functionality. * Introduce stock market support. ### Phase 3 — Multichain Expansion * Expand OMEN Utility toward multichain support. * Explore bridge integration for cross-chain access. * Expand marketing and community reach. * Pursue listings on CoinMarketCap and CoinGecko. Multichain and bridge integrations will depend on technical feasibility and security requirements. Third-party listings remain targets, not guaranteed outcomes. ### Phase 4 — Ecosystem Growth * Expand market intelligence capabilities. * Develop additional utility for $OMEN. * Strengthen platform integrations. * Continue improving the ecosystem as the platform grows. ### Ongoing Development Development priorities may evolve as the project progresses. Official channels will communicate significant milestones and feature availability. The roadmap represents the current direction of OMEN Protocol rather than a guarantee of delivery dates. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://omen-protocol.gitbook.io/omen-protocol-docs/roadmap/omen-protocol-roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.