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

# Verify a pool yourself

Check any oripa.xyz pool yourself: the card list is committed onchain before the first rip, the slot order is shuffled from a block hash no one knew in advance, and the full order is published when th

**TL;DR:** Before the first rip, oripa.xyz commits the pool's card list and the hash of a secret onchain. The slot order is then shuffled from that secret and the hash of the block the pool was created in, so oripa.xyz does not choose it. When the pool closes, the secret and the full order are published, and anyone can redo the shuffle.

## What is public before the pool opens

The full card list, each card's locked price and its price sources, the number of slots and the pool's index RTP. All of it is on the pool page, as a file called `commit.json`, before the first rip.

## What is committed onchain

When a pool is built, oripa.xyz writes the SHA-256 hash of `commit.json` to the Pool contract. `commit.json` holds the card list, every locked price and the hash of a secret. The pool page shows this hash with a link to the chain.

## How the order is set

The order is not chosen by oripa.xyz. Once the pool's creation transaction lands in a block, the slots are shuffled from the secret and that block's hash, which no one knew in advance. Only then does the pool open.

## What is revealed

When the pool closes, oripa.xyz publishes `pool.json`: the secret, the block used for the shuffle and the full slot order. Its location is recorded onchain. Anyone can download it.

## How to check

1. Download `commit.json` from the pool page and compute its SHA-256 over the exact bytes as downloaded (UTF-8 JSON; don't reformat it). Compare it with the hash in the pool's creation event onchain (`PoolCreated` on the Pool contract, or `pools(poolId)`).
2. After the pool closes, download `pool.json`. Check that the SHA-256 of its `secret` matches `secretHash` in `commit.json`.
3. Check that the block in `pool.json` is the block of the pool's creation transaction.
4. Redo the shuffle (`oripa-shuffle-v1`) from `sha256(secret ‖ block hash)` over the card list in `commit.json`, and check that it gives the slot order in `pool.json`.
5. Find your slot number in `pool.json` and confirm it is the card you received.

## What this proves

* The card list, including every locked price, was fixed before the first rip.
* The slot order was not chosen by oripa.xyz: it follows from a secret committed in advance and a block hash no one knew in advance.
* Your slot was assigned onchain and maps to the card at that slot.
* Nothing was repriced or swapped during the sale.


---

# 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/mechanics/verify.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.
