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

# Allowlist

The oripa.xyz allowlist: seven days of access from 2026-11-25 for wallets picked by random draw, each with the same spending cap and mint rate.

**TL;DR:** From 2026-11-25 to 2026-12-01, oripa.xyz is open only to wallets picked by random draw, each with the same spending cap. Allowlisted wallets get seven days of access and nothing else: the same mint rate and the same transfer schedule as every wallet after them.

## Why there is one

The first 5M USDC of cumulative loss mints at the highest rate the curve will ever offer. If that segment opened to everyone at once, the fastest and largest wallets would take most of it. So the first seven days are open only to wallets picked by random draw, and every one of them can spend the same amount on rips.

The seven days are also a live run at limited volume: the whole platform, from the first rip to the first reward payout, runs with real users and real cards before it opens to everyone.

## What allowlisted wallets get

Seven days of access, from 2026-11-25 to 2026-12-01, and nothing else. Every drawn wallet has the same spending cap, the same mint rate and the same transfer schedule as every wallet after it. There is no presale, discount or bonus allocation.

## What stays for open access

Allowlist volume is capped, and the rest of the flat segment opens to every wallet on 2026-12-02.

## How wallets are chosen

By random draw among registered wallets. Registration rules, the draw method and the drawn list are published before the allowlist opens.


---

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