We commit first.
Before your opening, the server generates a secret random seed and publishes its SHA-256 hash. This locks in the server’s input before you choose to open.
INR
Every product and every probability, visible before you open.
An independently verifiable receipt, after every spin.
Before your opening, the server generates a secret random seed and publishes its SHA-256 hash. This locks in the server’s input before you choose to open.
You can choose your own client seed. We combine it with the committed server seed and a unique nonce using HMAC-SHA256 to calculate the draw.
After the reveal, copy your server seed. Paste it below and we retrieve the opening details so your browser can check the commitment, draw, and prize.
These are the total chances for each rarity tier, shared across its products and wallet vouchers. Common receives 70.00% and Uncommon 25.00%. Every box includes all five tiers. The remaining 5.00% is shared by Rare, Epic, and Legendary. Each box shows the exact chance of every individual product.
Copy the revealed server seed from your opening result or collection item. We fill in the saved client seed, nonce, and odds, then independently reproduce your prize in this browser.
We retrieve this account’s saved opening. The fairness calculation runs locally in your browser.
Server and client seeds are UTF-8 strings. The HMAC key is the revealed hexadecimal server seed as text. For block 0 onwards, the message is clientSeed:nonce:block.
Read the SHA-256 digest as eight unsigned 32-bit, big-endian integers. Accept the first integer smaller than 4,294,000,000; if none qualifies, advance to the next block. Its remainder modulo 1,000,000 is the draw ticket for v2 receipts.
Starting at ticket 0, each product occupies a consecutive range equal to its weight. Weights total 1,000,000. The product whose interval contains the ticket is selected. The visual reel only displays this already determined result.
Earlier v1 receipts retain their original 10,000-ticket table, rejection limit of 4,294,960,000, and result. The verifier selects the calculation from the receipt’s algorithm version.
To verify the precommitment independently, retain the hash shown before opening and compare it with SHA-256 of the revealed seed. The receipt alone checks internal consistency; it does not independently establish when a hash was published.