> For the complete documentation index, see [llms.txt](https://docs.oripa.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oripa.xyz/readme.md).

# oripa.xyz docs

Documentation for oripa.xyz, onchain oripa for real trading cards on HyperEVM. How pools, rips, melts and the $ORIPA token work, and how to check them yourself.

**TL;DR:** oripa.xyz sells rips from pools of real trading cards, priced to a public index and paid in USDC on HyperEVM. Every card can be shipped or melted back for USDC, every rip that records a loss mints $ORIPA, and staked $ORIPA earns USDC from every rip on the platform.

{% hint style="info" %}
The allowlist opens on 2026-11-25 and open access starts on 2026-12-02. Contract addresses and audit reports are published at launch on [Contracts](https://docs.oripa.xyz/trust/contracts.md) and [Audits and bug bounty](https://docs.oripa.xyz/trust/audits.md).
{% endhint %}

## Start here

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What is oripa?</strong></td><td>Pools, rips, hits and misses.</td><td><a href="https://docs.oripa.xyz/getting-started/how-it-works.md">What is oripa?</a></td></tr><tr><td><strong>Getting started</strong></td><td>From an empty wallet to your first card.</td><td><a href="https://docs.oripa.xyz/getting-started/getting-started.md">Getting started</a></td></tr><tr><td><strong>Fees</strong></td><td>What you pay and where every USDC goes.</td><td><a href="https://docs.oripa.xyz/fees-and-parameters/fees.md">Fees</a></td></tr></tbody></table>

## Mechanics

* [How cards are valued](https://docs.oripa.xyz/mechanics/valuation.md): the index behind every price.
* [Melt and ship](https://docs.oripa.xyz/mechanics/melt-and-ship.md): what you can do with a card.
* [Reserve](https://docs.oripa.xyz/mechanics/reserve.md): the USDC that pays every melt.
* [Verify a pool yourself](https://docs.oripa.xyz/mechanics/verify.md): check that the pool you ripped is the pool you were shown.

## $ORIPA

* [$ORIPA](https://docs.oripa.xyz/token/oripa.md): what it is, in one table.
* [Every miss mints](https://docs.oripa.xyz/token/mint-curve.md): how a rip mints $ORIPA, and how the rate falls.
* [Rewards and staking](https://docs.oripa.xyz/token/rewards.md): the USDC that staked $ORIPA earns.
* [Transferability](https://docs.oripa.xyz/token/transferability.md): when $ORIPA can be transferred.

## Trust

* [Risks](https://docs.oripa.xyz/trust/risk.md): what can go wrong, and what the code enforces.
* [Contracts](https://docs.oripa.xyz/trust/contracts.md): every address, and who can do what.
* [Audits and bug bounty](https://docs.oripa.xyz/trust/audits.md): what has been checked, and how to report a bug.
* [Published figures](https://docs.oripa.xyz/trust/stats.md): every number we publish, and where to read it.
* [Legal and eligibility](https://docs.oripa.xyz/trust/legal.md): who operates oripa.xyz and who may use it.
* [Changelog](https://docs.oripa.xyz/trust/changelog.md): every change, newest first.

{% hint style="info" %}
Nothing in these docs is investment, legal or tax advice.
{% 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://docs.oripa.xyz/readme.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.
