> 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/getting-started/how-it-works.md).

# What is oripa?

Oripa (オリパ) is Japan's original-pack format: a pool of real cards sold one slot at a time. oripa.xyz runs it onchain, with every card list and price published before the first rip.

**TL;DR:** Oripa (オリパ, "original pack") is a Japanese format where a shop builds a pool of real cards and sells it one slot at a time. oripa.xyz runs that format onchain: every pool's cards and prices are public before the first rip, every card can be shipped or melted back for USDC, and a rip that records a loss mints $ORIPA.

## The format

In a Japanese card shop, an oripa is a box of packs the shop made itself. The shop lists the top cards on the box, you buy a pack, and you get one card. Most packs are worth less than the price; a few are worth much more.

oripa.xyz keeps the format and changes three things:

1. **The pool is public before you rip.** Every card, its locked price and its price sources are published, and the pool is committed onchain before the first rip. See [Verify a pool yourself](https://docs.oripa.xyz/mechanics/verify.md).
2. **Every card has a price you can sell it at.** Any card can be melted back to the platform for USDC at 85% of its index price. See [Melt and ship](https://docs.oripa.xyz/mechanics/melt-and-ship.md).
3. **A miss is not nothing.** When your card's locked price is below the rip price, the difference mints $ORIPA. See [Every miss mints](https://docs.oripa.xyz/token/mint-curve.md).

## How oripa.xyz works

A **pool** is a fixed set of cards sold at one rip price. A **rip** buys one slot in a pool and reveals the card in it. Every card carries an **index price**, a weighted median of its recent market prices. A revealed card can be shipped or **melted** back to the platform for USDC at 85% of its index price. Each wallet can select up to 5 cards a day for shipping; a card not selected within 24 hours of its rip is melted automatically.

When a pool is built, each card's index price at that moment is recorded as its **locked price**, which stays fixed while the pool is live. The locked price sets the pool's RTP, each rip's recorded loss and the reserve set aside for the card. Melting uses the index price on the day of the melt, which moves with the market.

## Hits and misses

Each rip is one of two outcomes:

* **Miss.** The card's locked price is below the rip price. The rip records a loss and mints $ORIPA.
* **Hit.** The card's locked price is at or above the rip price. The rip records no loss and mints nothing.

**Example.** A rip at 100 USDC reveals a card whose locked price is 20 USDC. The rip records a loss of 80 USDC and, at the opening rate, mints 800 $ORIPA to the user and 320 $ORIPA to the Vault. Melting pays 85% of the card's index price on the day of the melt, and the index moves with the market: at 20 USDC the melt pays 17 USDC; if the index rises to 25, it pays 21.25.

## What a pool returns

In every pool, the cards' locked prices add up to 85% of the rip price × the number of slots. If every card were melted at its locked price, the pool would return 85 × 0.85 = 72.25 USDC for every 100 USDC ripped. The other 27.75 USDC go to stakers: 5 as the rip fee and 22.75 as rip surplus, before any restock deduction for shipped cards (see [Rewards and staking](https://docs.oripa.xyz/token/rewards.md)). The platform keeps none. Cards whose index rises after the rip melt for more; cards whose index falls melt for less.

## Pools

Every pool is built to an index RTP of 0.85: the sum of its cards' locked prices ÷ (its rip price × its number of slots). There is no last-one bonus.

Before a pool opens, its page publishes the full card list, each card's locked price and price sources, the number of slots and the pool's index RTP; what one wallet can see, every wallet sees at the same moment. Pools do not linger: a pool with no rip for 30 minutes closes, and its unsold slots are rebuilt into new pools at prices re-locked to the current index. Melted cards return to inventory; shipped cards leave it.

How pools are stocked: [Card inventory](https://docs.oripa.xyz/mechanics/card-inventory.md).

## Next

* [Getting started](https://docs.oripa.xyz/getting-started/getting-started.md): connect, deposit and rip.
* [Fees](https://docs.oripa.xyz/fees-and-parameters/fees.md): where every USDC of the rip price goes.


---

# 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/getting-started/how-it-works.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.
