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

# Published figures

Every number oripa.xyz publishes, where to read it yourself, and how often it changes: mint rate, $ORIPA supply, reserve coverage, staking and activity.

**TL;DR:** The live numbers are on the oripa.xyz stats page (/stats). This page lists each one, where it comes from and how often it changes. Where a figure is onchain, the contract is the source of truth.

## Protocol

| Figure                                                                                      | Where                                       | Updates                    |
| ------------------------------------------------------------------------------------------- | ------------------------------------------- | -------------------------- |
| Cumulative recorded loss `H` and the current mint rate `R(H)`                               | $ORIPA contract; /stats                     | Every rip                  |
| $ORIPA supply: total, minted to users, minted to the Vault                                  | $ORIPA contract; /stats                     | Every rip                  |
| $ORIPA staked, number of stakers and how concentrated staking is                            | Staking contract; /stats                    | Every stake and unstake    |
| Reserve held, reserve required (`minHouseReserve`), coverage                                | Balance contract; /stats                    | Daily, at the index update |
| USDC paid to stakers: rip fees and rip surplus, last 24 hours, 7 days, 30 days and all time | Staking and Balance contract events; /stats | Every rip                  |

## Activity

| Figure                                                                           | Where  | Updates                |
| -------------------------------------------------------------------------------- | ------ | ---------------------- |
| Last 24 hours: USDC ripped, rips, $ORIPA minted, hit rate                        | /stats | Rolling 24 hours (UTC) |
| Pools built: number, slots, index RTP and recorded-loss ratio across all of them | /stats | Per pool               |
| Cards held back by the index each day for too few samples or sources             | /stats | Daily                  |

## Cards and pools

| Figure                                                                         | Where                                                                 | Updates                                                                     |
| ------------------------------------------------------------------------------ | --------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Each card: index price, sources, sample count, update time                     | The card's pool page                                                  | Daily                                                                       |
| Each pool: card list, locked prices, slots, index RTP, status, commitment hash | The pool's page                                                       | Fixed at build                                                              |
| Index methodology and its version                                              | [How cards are valued](https://docs.oripa.xyz/mechanics/valuation.md) | On change, listed on [Changelog](https://docs.oripa.xyz/trust/changelog.md) |

Figures on /stats are computed by oripa.xyz from the contracts and the index. Where a figure is onchain, the contract is the source of truth.


---

# 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/stats.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.
