> 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/reference/glossary.md).

# Glossary

Terms used across the oripa.xyz docs: rip, pool, index price, locked price, recorded loss, melt, reserve, Vault and more.

**TL;DR:** The terms used across these docs, each in one line.

| Term               | Meaning                                                                                                      |
| ------------------ | ------------------------------------------------------------------------------------------------------------ |
| Pool               | A fixed set of cards sold at one rip price                                                                   |
| Rip                | Buying one slot in a pool and revealing the card                                                             |
| Rip price          | The price of one rip                                                                                         |
| Index price        | Weighted median of a card's recent completed sales, C2C listings and shop prices                             |
| Locked price `P_c` | A card's index price recorded when its pool is built; fixed while the pool is live                           |
| Pool index RTP     | Sum of locked prices in a pool ÷ (rip price × number of slots)                                               |
| Miss / Hit         | A rip whose card's locked price is below / at or above the rip price                                         |
| Recorded loss `L`  | Rip price − locked price, floored at zero                                                                    |
| `H`                | Cumulative recorded loss across the platform                                                                 |
| `R(H)`             | Mint rate in $ORIPA per USDC of recorded loss                                                                |
| `T`, `S`           | Flat-segment length and decay parameter of `R(H)`                                                            |
| Melt               | Selling a revealed card to the platform for USDC                                                             |
| Reserve            | A single USDC balance that pays every melt, held at 0.85 × the index of every outstanding card               |
| Rip fee            | 5% of every rip price, paid to stakers at the rip                                                            |
| Rip surplus        | Rip price − rip fee − 0.85 × locked price, paid to stakers through a running balance                         |
| Restock ratio      | A card's replacement cost over its locked price; capped at 1.00                                              |
| oripa.xyz balance  | The USDC balance you hold on the platform, in the Balance contract                                           |
| Session key        | A key your wallet authorizes once so rips, melts, stakes and claims need no wallet popup; it cannot withdraw |
| Vault              | Where the platform's allocation is minted, 40 per 100 user mints; released 2027-03-16 to 2027-08-31          |
| Timelock           | The contract that delays every upgrade and admin action by 48 hours                                          |
| Guardian           | A key that can only pause deposits, rips and shipping-fee charges, and freeze operator payouts               |


---

# 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/reference/glossary.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.
