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

# Transferability

When $ORIPA becomes transferable: transfers open on 2027-01-13, with 50% of earlier mints released at once and the rest in 13 tranches to 2027-07-14.

**TL;DR:** $ORIPA is non-transferable at launch. Transfers open on 2027-01-13: half of what a wallet minted before that date becomes transferable at once, and the other half is released in 13 tranches every 14 days to 2027-07-14. $ORIPA minted from 2027-01-13 is transferable at mint.

$ORIPA is non-transferable at launch. It can be minted, staked and used to claim rewards; it cannot be traded, transferred or listed.

## The schedule

Transfers open on **2027-01-13** (00:00 UTC), six weeks after open access. On that date, for every wallet:

* 50% of the $ORIPA minted to the wallet before 2027-01-13 becomes transferable immediately.
* The other 50% is released in 13 equal tranches, one every 14 days, the first on 2027-01-27 and the last on 2027-07-14.
* $ORIPA minted on or after 2027-01-13 is transferable at mint.

The same schedule applies to every wallet. Transferring requires the balance to be unstaked; locked $ORIPA can still be staked and still earns rewards.

## How much of a balance is locked

$$
k = \min\left( \left\lfloor \frac{\text{days since 2027-01-13}}{14} \right\rfloor,\ 13 \right)
$$

$$
\text{locked} = 0.5 \times M\_0 \times \left(1 - \frac{k}{13}\right) \qquad \text{transferable} = \text{balance} - \text{locked}
$$

$$M\_0$$ is the $ORIPA minted to the wallet before 2027-01-13.

The transfer-opening date and the release schedule are written into the token contract at deployment and can only be set once.


---

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