> 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/faq.md).

# FAQ

**Do I need $OVRO to play?** Not during Genesis: rounds are open to every wallet. After the token activation, you need the minimum $OVRO balance shown on the site.

**What do I pay with?** ETH on Robinhood Chain. Gas is also paid in ETH.

**How are winners picked?** By the drand randomness beacon, verified inside the contract. See [Randomness](/ovro-docs/protocol/randomness.md).

**Can the team pick the winner or take the pool?** No. Winner selection is cryptographic and on-chain, and no role can withdraw ETH owed to players.

**When is the winner paid?** In the same transaction that reveals the result. If your wallet cannot receive ETH automatically, the prize is credited and you can withdraw it from the site.

**What if a round does not fill?** When the timer ends, the round draws if it has enough players; otherwise it is cancelled and every ticket is refunded in full.

**What happens to fees?** 5% goes to the treasury multisig and 5% to the $OVRO buyback & burn. Fees are capped at 20% by the contract.

**Where does the Genesis buyback reserve go?** It stays in the raffle contract until $OVRO launches. It can only be forwarded to the buyback executor, which buys $OVRO on the market and burns it.

**How much does it cost to play?** One ticket costs 0.001 ETH under the current rules, plus a few cents of gas on Robinhood Chain.

**Can I use my phone?** Yes. Open ovro.fun in the built-in browser of your wallet app (MetaMask, Rabby and others). Regular mobile browsers cannot reach a wallet, because OVRO does not use WalletConnect.

**How many tickets can I buy?** Up to 10 per wallet per round under the current rules, as long as tickets are left. After the $OVRO activation, larger holders can get higher limits.

**Why does "Chance now" show 100%?** It is your share of the tickets sold so far. If you are the first buyer, you hold all of them. "Chance at sell-out" shows your share if the round sells out.

**What if the automation or the website is down?** Anyone can close a round, reveal a winner, claim refunds and withdraw prizes directly from the explorer. See [Using OVRO without the website](/ovro-docs/protocol/without-the-website.md).

**Can I verify that a winner was fair?** Yes, from public data only. See [Verify a draw](/ovro-docs/protocol/verify-a-draw.md).

**Can the rules change in the middle of a round?** No. Round rules are immutable, and new rules only apply to rounds that open later, after a 48-hour public timelock.

**What happens to Genesis players when $OVRO launches?** The round in progress finishes under Genesis rules. From the next round, entering requires the minimum $OVRO balance.

**Where do I get $OVRO?** Only on Pons V2 after the launch. The official contract address will be published on the [Contracts](/ovro-docs/security/contracts.md) page and on the website.

**Is OVRO audited?** Not yet. An external audit is planned. See [Security model](/ovro-docs/security/security.md).

**Is this available in my country?** You are responsible for complying with the laws that apply to you. See [Risks & disclaimer](/ovro-docs/resources/risks.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/resources/faq.md?ask=<question>&goal=<user_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.