Roobet Originals verifier
Paste a revealed Roobet server seed, client seed and nonce — or a Crash game hash. This page recomputes the selected Original with Roobet’s published /fair sandboxes, not Stake, Shuffle, BC.Game or Rainbet mappings. It is not on the unified /verify page yet. After the page loads, nothing is sent to a server.
What this page implements
Crash is a hash chain
Roobet Crash does not use your client seed. Each round’s game hash is the SHA-256 of the next hash. The crash point is HMAC-SHA256(key = gameHash, message = salt) with salt 0000000000000000000fa3b65e43e4240d71762a5bf397d5304b2596d116859c (Bitcoin block 610546). Instant 1.00× when that HMAC hex is divisible by 25.
generateFloats
Dice, Mines, Plinko, Limbo, Keno, Towers and Roulette key HMAC-SHA256 with the revealed server seed and sign clientSeed:nonce:round. Four bytes become one float: b0/256 + b1/65536 + b2/2²⁴ + b3/2³². That is the helper in Roobet’s /fair sandboxes.
Not on this page
Coinflip is two-player. Blackjack needs the actions hash. Mission Uncrossable, Slide, High Striker and Wheel stay off until their extra tables can be labelled without guessing.
Not the unified calculator
Stake, Shuffle and BC.Game stay on /verify. This URL is Roobet-only so you can check the numbers against roobet.com/fair 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 Crash a different form?
Crash is a public hash chain shared by every player in the round. Your client seed never enters that calculation, so this page asks only for the game hash from that round.
Why is Dice 0.00–100.00 instead of 0.00–99.99?
The official dice-yqlpw6 snippet maps floor(float × 10001) / 100. That is Roobet’s published range. Do not use Stake’s 10000 map here.
My result doesn’t match Roobet. What went wrong?
Check you pasted the revealed server seed, not the hash; that the nonce belongs to that bet; and that Crash used the round game hash. A genuine mismatch is worth reporting — and is exactly why this page is still off the unified /verify hub.