Rainbet Originals verifier
Paste a revealed Rainbet server seed, client seed and nonce. This page recomputes the selected Original with Rainbet’s published HMAC uint32 stream and rejection sampling — not Stake, Shuffle, BC.Game or Goated mappings. After the page loads, nothing is sent to a server.
What this page implements
HMAC uint32 stream
Rainbet keys HMAC with the revealed server seed and signs clientSeed:nonce:<gameLabel>:step. Each digest is split into big-endian 32-bit integers. Unbiased integers use rejection sampling: 2³² − (2³² % range).
SHA-512 vs SHA-256
The official Game Verifier snippets are not all one hash. Mines, Keno, Blackjack and War use HMAC-SHA512. Dice, Limbo, Plinko, Hilo, Tower, Chicken Cross, Wheel, Rock Paper Scissors and Moles use HMAC-SHA256. This page follows each snippet.
Not on this page
Crash and Case Opening have no Game Verifier snippet. Case Battles and EOS Roulette use EOS blockchain blocks instead of client/server seeds, so they are omitted rather than guessed.
Not the unified calculator
Stake, Shuffle and BC.Game stay on /verify. This URL is Rainbet-only so you can check the numbers before any tab is added there.
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 is Mines labelled HMAC-SHA512 when Dice is SHA-256?
Those are the algorithms in Rainbet’s published snippets on /provably-fair/game-verifier/*. Mixing them would produce the wrong board or roll.
What about Plinko multipliers?
The official Plinko snippet ships placeholder multiplier tables (all 1s). The path and bucket index are the published random outcome, so that is what this page shows.