> 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/protocol/rounds.md). # Rounds ## Lifecycle ``` OPEN ──(sold out, or timer ended with enough players)──▶ FULL ──▶ RANDOMNESS REQUESTED ──(beacon verified)──▶ SETTLED ──▶ next round OPEN OPEN ──(timer ended with too few players)──▶ CANCELLED (full refunds) ──▶ next round OPEN ``` Only one round is live at a time. Every state change is validated by the contract. ## Parameters Each round uses an **immutable configuration** that is fixed when the round opens. Nobody can change the rules of a round in progress. | Parameter | Current value\* | | ------------------ | -------------------------------------------------- | | Ticket price | 0.001 ETH | | Tickets per round | 20 | | Timer | 24 h, starting with the first ticket | | Minimum players | 2 | | Tickets per wallet | 5 (from 100,000 $OVRO) · 10 (from 1,000,000 $OVRO) | | Split | 90% prize · 5% treasury · 5% buyback | | Eligibility | Holding at least 100,000 $OVRO | \* Always check the live values on [ovro.fun](https://ovro.fun) → **● ONCHAIN**. They are read directly from the contract. ## Buying tickets * Pay exactly `tickets × ticket price` in ETH. * Your tickets are recorded on-chain as a contiguous range of ticket numbers. * **Your chance** = your tickets ÷ tickets sold. ## Closing and the draw * **Sold out**: the draw starts in the same transaction as the last ticket. * **Timer ended**: anyone can press *Close round*. With at least the minimum number of players the draw starts; otherwise the round is cancelled and **every ticket is refundable in full**. * The draw commits to a future randomness beacon. Once that beacon is published, **anyone** can submit it (the site has a *Reveal winner* button, and the automation does it within seconds). ## Winner `winning ticket = randomness mod tickets sold`. The owner of that ticket number wins. The prize is sent automatically. If the winner's wallet cannot receive ETH (for example, a contract that rejects it), the prize is credited and can be withdrawn at any time. ## Safety valves * **Refunds**: cancelled rounds refund 100% of ticket cost, with no fee. * **Stuck draw**: if randomness is not delivered within the timeout, anyone can re-request it. If a round is still not settled after 7 days, anyone can cancel it, and everyone is refunded. * **Pause**: the guardian multisig can pause **ticket sales only**. Draws, refunds and withdrawals always keep working. --- # 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/protocol/rounds.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.