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

# Getting started

Get started on oripa.xyz: what you need, how to get USDC onto HyperEVM, and the five steps from connecting a wallet to your first card.

**TL;DR:** You need an EVM wallet, USDC on HyperEVM and a little HYPE for deposits and withdrawals. Connect once, deposit USDC, rip, then ship or melt your card within 24 hours.

## What you need

* An EVM wallet: MetaMask, Rabby, Rainbow or any WalletConnect wallet.
* USDC on HyperEVM (Hyperliquid's EVM chain).
* A little HYPE in your wallet. You need it only for deposits and withdrawals. Rips, melts, stakes and claims never need gas.

## Getting USDC onto HyperEVM

No bridge needed. On the Deposit screen, pick the chain your USDC is on (Arbitrum, Base, Ethereum or Solana) and sign once on that chain. Circle's CCTP moves it straight into your oripa.xyz balance: within seconds for a small Circle fee, or free in about 15 minutes or more.

## Five steps

1. **Connect.** Pick your wallet and sign once. That signature registers a session key. From then on every rip, melt, stake and claim is one click and never opens your wallet. The session key cannot withdraw. It expires after 7 days; sign again to renew.
2. **Deposit.** Send USDC from your wallet into your oripa.xyz balance. The first time, approve USDC, then confirm. Minimum deposit: 10 USDC.
3. **Rip.** Open a pool. The page shows every card in it, each card's locked price, the number of slots and the pool's index RTP. Press Rip. Your card appears within about ten seconds.
4. **Ship or melt.** Within 24 hours of the rip, select the card for shipping or melt it for USDC at 85% of its index price that day. A card not selected within 24 hours is melted automatically. You can select up to 5 cards a day for shipping.
5. **Stake and claim.** A rip whose card's locked price is below the rip price mints $ORIPA to your wallet. Stake it on the Stake page to earn USDC from every rip on the platform. Claim rewards into your balance at any time.

Withdraw USDC from your balance to your wallet whenever you like. Withdrawals need your wallet signature and are never paused.

## When

|             |                                                          |
| ----------- | -------------------------------------------------------- |
| Allowlist   | 2026-11-25 to 2026-12-01, wallets drawn from registrants |
| Open access | 2026-12-02                                               |

Allowlist rules: see [Allowlist](https://docs.oripa.xyz/token/allowlist.md).

## Next

* [Fees](https://docs.oripa.xyz/fees-and-parameters/fees.md): what you pay and where it goes.
* [Verify a pool yourself](https://docs.oripa.xyz/mechanics/verify.md): check a pool yourself.
* [Risks](https://docs.oripa.xyz/trust/risk.md): what can go wrong.


---

# 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/getting-started/getting-started.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.
