> 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/mechanics/reserve.md).

# Reserve

The oripa.xyz reserve: a single USDC balance that pays every melt, held at 0.85 × the current index of every outstanding card.

**TL;DR:** Every rip sets aside 85% of the locked price of the card pulled. The reserve is one USDC balance that pays every melt, and the contract lets the platform withdraw only what sits above the required amount.

Every rip sets aside 85% of the locked price of the card pulled as reserve. The reserve is a single USDC balance that pays every melt.

The amount required is 0.85 × the current index of every outstanding card, recomputed every day as the index updates and written to the contract as `minHouseReserve`. Shipping a card releases its share.

The contract lets the platform withdraw only what sits above the required reserve. The platform's policy is to leave it there: USDC freed when the index falls first pays any rip surplus still owed to stakers, and the rest stays in the reserve to cover later rises.

## If the reserve falls short

While the reserve covers every outstanding card, there is no limit on melts. On a day it does not, melts beyond what it covers wait and are paid in order once it does, at the price quoted when each melt was requested. Your oripa.xyz balance and your withdrawals are not affected.

## Where to read it

The reserve held, the reserve required and coverage are read from the Balance contract and shown on [Published figures](https://docs.oripa.xyz/trust/stats.md).


---

# 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/mechanics/reserve.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.
