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

# $ORIPA

$ORIPA is the token of oripa.xyz: minted only by rips that record a loss, staked to earn USDC from every rip, and non-transferable until 2027-01-13.

**TL;DR:** $ORIPA is the token of oripa.xyz. It is minted by ripping: a rip whose card's locked price is below the rip price mints $ORIPA against the difference. It is staked to earn USDC from every rip on the platform, and it is non-transferable until 2027-01-13. There is no presale or private round; before the first rip, no $ORIPA exists.

{% hint style="info" %}
These pages describe protocol mechanics and the parameters set in the contracts. They are not investment advice and contain no forecasts. Live onchain figures (supply, `H`, reserve, rewards) can be read directly from the contracts; index prices are published daily.
{% endhint %}

## In one table

|                     |                                                                                                                            |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| How it is minted    | Only by a rip that records a loss, at the rate `R(H)`. See [Every miss mints](https://docs.oripa.xyz/token/mint-curve.md). |
| What it earns       | USDC from every rip, when staked. See [Rewards and staking](https://docs.oripa.xyz/token/rewards.md).                      |
| Supply              | Approaches 770M and never reaches it: 550M to users, 220M to the Vault                                                     |
| Platform allocation | 40 per 100 user mints, to the Vault. See [Vault](https://docs.oripa.xyz/token/vault.md).                                   |
| Transfers           | None until 2027-01-13. See [Transferability](https://docs.oripa.xyz/token/transferability.md).                             |
| First wallets       | Seven-day allowlist from 2026-11-25. See [Allowlist](https://docs.oripa.xyz/token/allowlist.md).                           |

## Key dates

| Date (UTC)               | What happens                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------- |
| 2026-11-25               | Allowlist opens. First rip.                                                               |
| 2026-12-02               | Open access.                                                                              |
| 2027-01-13               | Transfers open: 50% of earlier mints transferable; the rest in 13 tranches to 2027-07-14. |
| 2027-03-02               | The Vault's balance on this date is locked for release.                                   |
| 2027-03-16 to 2027-08-31 | The Vault's locked balance is released in 13 tranches.                                    |

## Read more

* [Design notes](https://docs.oripa.xyz/reference/design-notes.md): what the platform earns, and why minting has a cost.
* [Parameters](https://docs.oripa.xyz/fees-and-parameters/parameters.md): every value in one table.


---

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