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

# Wallet setup

Add Robinhood Chain to your wallet and get ETH for tickets and gas.

OVRO runs on **Robinhood Chain**. You need a browser wallet connected to that network and some ETH on it.

## 1. Pick a wallet

Any EVM browser wallet works. We test with **MetaMask** and **Rabby**.

On a phone, open [ovro.fun](https://ovro.fun) inside your wallet app's built-in browser (MetaMask, Rabby and most other wallets have one). OVRO does not use WalletConnect or any other relay service, so a regular mobile browser cannot connect to your wallet.

## 2. Add Robinhood Chain

Press **Connect** on [ovro.fun](https://ovro.fun). If your wallet does not know the network yet, the site asks it to add Robinhood Chain and switch to it. Approve both prompts.

To add it manually:

| Field           | Value                                     |
| --------------- | ----------------------------------------- |
| Network name    | Robinhood Chain                           |
| Chain ID        | `4663`                                    |
| Currency symbol | `ETH`                                     |
| RPC URL         | `https://rpc.mainnet.chain.robinhood.com` |
| Block explorer  | `https://robinhoodchain.blockscout.com`   |

## 3. Get ETH on Robinhood Chain

Tickets and gas are paid in the network's native **ETH**. ETH on Ethereum, Arbitrum or another network is a different balance: it has to be moved to Robinhood Chain first, either by withdrawing from an exchange that supports Robinhood Chain or through a bridge.

{% hint style="warning" %}
Do not send WETH, USDC or other tokens expecting to buy tickets with them. Only native ETH is accepted.
{% endhint %}

## How much ETH you need

|                    | Approximate cost                                     |
| ------------------ | ---------------------------------------------------- |
| One ticket         | 0.001 ETH (current round rules)                      |
| Gas for a purchase | about 180,000 gas, a few cents at current gas prices |

Check the live ticket price on the site before buying: it is read from the contract.

## Safety checklist

* The only website is **ovro.fun**. Bookmark it.
* OVRO never asks for your seed phrase, private key or a signature to "verify" your wallet.
* A ticket purchase is a normal transaction to the raffle contract listed on the [Contracts](/ovro-docs/security/contracts.md) page, with the exact ETH amount shown in the purchase window. Reject anything else.


---

# 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/wallet-setup.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.