> 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/design-notes.md).

# Design notes

Why oripa.xyz is built the way it is: what the platform earns, why the index is the price the platform owes, why minting has a cost, and how rewards are pooled.

**TL;DR:** The platform keeps none of the rip price and is paid only in $ORIPA through the Vault. $ORIPA is minted only by a rip that records a loss, and the USDC it earns is pooled across all stakers.

## What oripa.xyz earns

None of the rip price. The platform's stake in the protocol is its allocation to the Vault, minted in $ORIPA alongside every user mint and released on its own schedule. The platform is paid in the same asset as its users.

## The index is the price the platform owes

Every melt is paid at the index on the day of the melt, every reserve is held at it, and every locked price is taken from it when a pool is built. Each card's price and sources are public, and every pool's card list and locked prices are published before its first rip. A later change in the index changes what a card melts for, never the loss a rip recorded.

## Minting has a cost

$ORIPA is only minted by a rip that records a loss. The cheapest route is to rip and melt, and a melt returns less than the rip price; the difference is the cost of the $ORIPA minted.

## Rewards go back to the users who rip

Everything a rip pays beyond the reserve for its card goes to wallets holding staked $ORIPA, and $ORIPA is only minted by ripping. USDC from a rip goes to all stakers: a staker receives the same share of every rip's payout, its own rips included, as it holds of staked supply. No wallet recovers a fixed share, or all, of its own loss, and the share of the earliest wallets falls with every wallet that mints after them.


---

# 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/design-notes.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.
