> For the complete documentation index, see [llms.txt](https://ovro.gitbook.io/ovro-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ovro.gitbook.io/ovro-docs/resources/roadmap.md). # Roadmap No dates are promised. Each step ships when it is ready and tested. ## ✅ Built * Raffle protocol: rounds, ETH tickets, escrow, refunds, automatic payouts * On-chain verified randomness (drand evmnet) * Buyback & burn executor for Pons V2 and Uniswap v4 * Timelocked multisig governance and guardian pause * Website with live on-chain data, round history and transparency panel * Automation (keeper) and monitoring ## ▶ Now — Genesis * Live on Robinhood Chain mainnet since 14 September 2026 * Open mainnet rounds with real ETH * Buyback reserve accumulating for $OVRO ## Next — $OVRO * $OVRO fair launch on Pons V2 * Token activation: holder-only rounds, Genesis reserve bought back and burned * Tiered ticket limits for larger holders ## Later * External security audit * Special holder rounds (larger pools, different ticket prices) * **Raffles for any Robinhood Chain token**: projects create rounds gated by their own token, with ETH tickets and ETH prizes; the protocol fee contributes to the $OVRO buyback * $OVRO-based governance over protocol parameters --- # 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://ovro.gitbook.io/ovro-docs/resources/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.