Gamdom Originals verifier
Paste a published Gamdom game hash, or a revealed server seed, client seed and nonce. This page recomputes the selected Original with Gamdom’s published CodeSandbox snippets — not Stake, Shuffle or Duel mappings. After the page loads, nothing is sent to a server.
What this page implements
Two families
Crash, Roulette and Hilo use a reverse SHA-256 hash chain. Dice, Mines, Limbo, Plinko, Keno, Pocket Dice, Blackjack, Towers, Chicken and Twist use a revealed server seed, your client seed and a nonce.
HMAC-SHA512 seeds
Seed-pair games sign clientSeed-nonce with the revealed server seed (Chicken is the exception: clientSeed:nonce:lane). That is the construction in Gamdom’s Game Verifier sandboxes.
Crash cutoff
The Crash snippet on this page is the current one (after 2 January 2026). Older rounds need Gamdom’s previous sandboxes — the in-game Verify button still points at the matching era.
Not the unified calculator
This URL is Gamdom-only so you can check the numbers before any tab is added there. It is not on the unified /verify page yet. Stake, Shuffle, BC.Game and the other live tabs stay on /verify.
Does any of my data leave this page?
No. After the page loads, hashing runs through the browser Web Crypto API. Seeds are not posted anywhere.
Why do Crash, Roulette and Hilo ask for a game hash?
Those three are multiplayer tables. Gamdom publishes the round hash when it ends. SHA-256 of that hash must equal the previous round’s hash. Your personal client seed is not part of those three official snippets.
My Dice or Mines result does not match. What now?
Use the revealed server seed, not the hashed commitment. Check the nonce belongs to that pair, and that you have not mixed a Crash game hash into a seed-pair game. A genuine mismatch is worth reporting to Gamdom.