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

# $OVRO

|               |                                                                                                                                          |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Name / ticker | OVRO / OVRO                                                                                                                              |
| Chain         | Robinhood Chain                                                                                                                          |
| Launchpad     | Pons V2                                                                                                                                  |
| Pair          | ETH                                                                                                                                      |
| Supply        | Fixed. The whole supply is minted into the Pons bonding curve at launch                                                                  |
| Contract      | [`0x7F9eF3a7e3dC205E4F13a48C1526A823FFb6Fe3e`](https://robinhoodchain.blockscout.com/address/0x7F9eF3a7e3dC205E4F13a48C1526A823FFb6Fe3e) |
| Launched      | 21 September 2026, creator tax 0%                                                                                                        |

## Fair launch on Pons V2

* No presale, no private round, no team allocation minted to anyone. Every wallet, including the team's, can only acquire $OVRO by buying from the public curve or pool, and every purchase is visible on-chain.
* Trading happens on the Pons bonding curve until it sells out. The liquidity then graduates to a Uniswap v4 pool and is **locked permanently** by Pons.
* Pons applies its own trading fee and a short anti-sniping tax in the first seconds after launch. Creator tax, if any, is fixed at launch and can never be raised. Current values are readable on-chain from the Pons curve.

## Utility

1. **Access.** Holding the minimum $OVRO balance is required to enter raffle rounds after Genesis.
2. **Higher limits.** Larger balances can unlock higher per-wallet ticket limits.
3. **Buyback & burn.** A share of every round's ETH pool buys $OVRO on the market and burns it. See [Buyback & burn](/ovro-docs/token/buyback.md).
4. **Holder rounds.** Special rounds for holders can run alongside regular rounds.
5. **Governance (planned).** Protocol parameters are controlled by a multisig behind a timelock today; $OVRO-based governance is on the roadmap.

{% hint style="warning" %}
$OVRO is a utility token for participating in the protocol. It is not a share, does not entitle holders to revenue or profits, and carries no promise of value. Its market price is set by trading and can go to zero. See [Risks](/ovro-docs/resources/risks.md).
{% endhint %}


---

# 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/token/ovro-token.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.