> 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/getting-started/claims.md). # Refunds & prizes How winners are paid and how refunds work when a round is cancelled. ## Prizes The winner receives the prize **in the same transaction that selects the winner**. No claim is needed. The contract sends the prize with a fixed gas allowance. A normal wallet always accepts it. If the winner is a smart contract that rejects ETH or needs more gas, the transfer does not revert the draw: the prize is **credited** to the winner instead. A credited prize is shown on the site and can be withdrawn at any time with **Withdraw**. It never expires. ## Refunds A round is cancelled when: * the timer ends with fewer than the minimum number of players (currently 2); * randomness is not delivered for 7 days after the round closed (anyone can then cancel it); * the guardian cancels it while sales are paused and before randomness was requested. Every ticket of a cancelled round is refundable **in full, with no fee**. Press **Claim refund** on the site. Each wallet claims once per round, and refunds do not expire. ## Who can touch this money Nobody except you. The contract keeps a running total of every wei it owes to players: escrowed tickets, credited prizes and refunds. No admin role can withdraw it. See [Security model](/ovro-docs/security/security.md). ## Without the website Refunds and withdrawals are plain contract calls: `claimRefund(roundId)` and `withdraw()`. See [Using OVRO without the website](/ovro-docs/protocol/without-the-website.md). --- # 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/getting-started/claims.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.