OPEN THE RECEIPT
Check the landing.
Your client seed. The server’s commitment. One reproducible result.
Before you play
- Open the arcade, select your paper or Bitcoin mode, and open Receipts. Save the next commitment before placing an individual round. At the shared roulette table, use Round proof & rules to save the pre-roll table commitment before joining.
- Choose your own client seed in Profile → Your randomness seed. You can generate one here and paste it into that field. The seed is sent with your next round; generating it here does not change your account.
- After settlement, copy the saved receipt JSON and paste it below. Compare it with the commitment you saved before that round.
Individual games publish SHA-256 of the server seed text before play and reveal that seed after settlement. HMAC-SHA256 combines the revealed seed with your exact client seed, nonce, game, choice and version. Shared roulette publishes a separate commitment for each table round; its HMAC uses the revealed table seed, round ID and hash of accepted public player keys, client seeds, stakes and chips. Rejection sampling produces the saved outcome; the published payout rules determine the gross return.
Client seed & SHA-256
This tool hashes your client seed. The server commitment hashes a separate, secret server seed. These two hashes have different roles.
Verify a receipt
Paste one individual-game receipt, a settled jackpot round, or a revealed shared roulette round. Historical versions use their saved rules. Seed and receipt inputs stay in this browser; they are not sent by this tool.
Algorithm & source hashes
Loading the published algorithm…
What these checks establish
A matching check reproduces the result from the disclosed inputs and checks the commitment and payout. The pre-play comparison establishes continuity with the hash you recorded before play. Without that independently saved hash, a receipt alone does not establish when the commitment was published.
Consistent JSON can be fabricated. This tool does not authenticate a receipt’s origin, prove how the secret seed was generated, detect seed searching before a commitment or selective aborted rounds, or certify that a server executed the published source. Browser randomness and source hashes are not an outside audit or certification. Verification does not predict future outcomes or remove the published house advantage.
Read the full game rules, chances and payouts