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

# Vault

The oripa.xyz Vault: the platform's allocation of 40 $ORIPA per 100 user mints, not staked, and released in 13 tranches from 2027-03-16 to 2027-08-31.

**TL;DR:** For every 100 $ORIPA minted to users, 40 are minted to the Vault as the platform's allocation. Vault $ORIPA is not staked and earns no rewards. Its balance on 2027-03-02 is released in 13 tranches from 2027-03-16 to 2027-08-31.

For every 100 $ORIPA minted to users, 40 are minted to the Vault as the platform's allocation. $ORIPA in the Vault is not staked and earns no rewards.

## Release

The Vault's balance on **2027-03-02** (00:00 UTC), three months after open access, is released in 13 equal tranches every 14 days: the first on **2027-03-16**, the last on 2027-08-31. None of that balance leaves the Vault before 2027-03-16.

$ORIPA minted to the Vault after 2027-03-02 is not part of the locked balance: like user mints from 2027-01-13, it is transferable at mint.

The Vault ratio, the Vault address and the release schedule are set once at deployment. See [Contracts](https://docs.oripa.xyz/trust/contracts.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/token/vault.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.
