> 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/trust/risk.md).

# Risks

What can go wrong on oripa.xyz and what happens to you if it does: card prices, the index, the reserve, smart contracts, admin keys, session keys, physical cards and $ORIPA.

**TL;DR:** Most rips reveal a card worth less than the rip price, and card prices move after the rip. This page lists what can go wrong, what the code enforces, and what is a platform policy.

## Card prices move

Melt pays 85% of a card's index price on the day you melt. A card that falls after your rip melts for less; one that rises melts for more. The locked price you saw on the pool page sets the rip's recorded loss and the reserve set aside at the rip, not the melt price.

## The index is computed by oripa.xyz

Locked prices, melt payouts and recorded loss all derive from the index, and oripa.xyz computes it. What you can check: every card's price, sources and update time are public before they are used, and every pool's locked prices are published before its first rip. If you believe a price is wrong, contact support (see [About oripa.xyz](https://docs.oripa.xyz/getting-started/about.md)).

## The reserve can fall short

USDC is held against every outstanding card at 0.85 × its index. If the index rises faster than the reserve, melts settle up to what the reserve covers that day and the rest queue in order. Queued melts are paid in full, at the price quoted when each was requested, as the reserve is restored. Your oripa.xyz balance and your withdrawals are not affected by the queue.

## Smart contracts

The contracts are upgradeable behind a 48-hour timelock. An upgrade or a bug could affect funds in the contracts. What reduces this: audits ([Audits and bug bounty](https://docs.oripa.xyz/trust/audits.md)), a bug bounty, and the rule that withdrawals cannot be paused.

What the code enforces:

* Withdrawals have no pause switch.
* The Guardian's pause stops only deposits, rips and shipping-fee charges; staking (stake, unstake, claim) has no pause.
* The rip fee and the mint curve (`T`, `S` and the opening rate) are fixed at deployment.
* $ORIPA is minted only for the recorded loss of a debited rip, never more than the rip's price, at the curve's rate.
* Platform withdrawals from the reserve cannot take it below the required reserve.
* A session key cannot withdraw.

Changing any of this needs an upgrade through the 48-hour timelock.

## Admin keys

**Admin.** A 2-of-3 Safe (three signers, each a distinct role: engineering lead, operations lead and an independent signer, each holding their own key) acting only through a 48-hour timelock. The Safe proposes, executes and can cancel; no one else can. It can upgrade the contracts, change the limits listed under [Who can do what](https://docs.oripa.xyz/trust/contracts.md#who-can-do-what), and lift a pause.

**Guardian.** A hardware wallet that can act immediately, but only to stop things: pause deposits, rips and shipping-fee charges, and freeze the operator's melt credits and reward funding. Only the admin can undo either, through the timelock.

**Treasurer.** The same Safe. The contract lets it 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.

**Hot keys run by oripa.xyz.** The relayer submits rips and shipping fees that you signed. The operator settles rips, credits melts, moves USDC from the reserve to the stakers' reward balance within a daily cap, and creates pools. The reserve writer records the required reserve once a day. None of them can take USDC out of your balance except for a rip or fee you signed.

**What no key can do** without a contract upgrade (visible 48 hours ahead): pause withdrawals, move USDC out of your balance, or mint $ORIPA other than for a rip's recorded loss.

## Your session key

If someone gets your session key, they can spend your oripa.xyz balance on rips, melt your cards into your balance, and claim your rewards into your balance. They cannot withdraw. Revoke the key from the account menu if you are on a shared device.

## Physical cards

Cards are held in the oripa.xyz vault until shipped. A card can be lost or damaged in storage or in transit; see [Physical cards](https://docs.oripa.xyz/mechanics/physical-cards.md). Duties, taxes and customs delays at your border are outside oripa.xyz's control.

## $ORIPA

* It is non-transferable until 2027-01-13 and then released on a schedule. You cannot sell it before that date.
* The mint rate only falls as cumulative loss grows. Later rips mint less per USDC than earlier ones.
* Staking rewards come from rips on the platform. If there are few rips, rewards are small; if there are none, rewards are zero.
* $ORIPA has no promise of value. The platform's own stake is the Vault, so the platform's interest is aligned with holders; nothing is promised to them.

## The platform

oripa.xyz can pause rips and deposits in an emergency. In that state you can still withdraw your balance and still hold your cards.

## Where you are

Some regions are restricted. See [Legal and eligibility](https://docs.oripa.xyz/trust/legal.md). Rules in your jurisdiction may change what oripa.xyz can offer you.

Nothing here is investment, legal or tax advice.


---

# 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/trust/risk.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.
