Calculate the reference result from a revealed server seed, client seed and nonce.
Reference
Enter the full hash saved before play. A hash copied afterwards does not establish earlier timing. Why timing matters
Reference implementation from published HMAC rules and captured fairness code. The example uses explicitly synthetic seeds and is not a casino bet. A hashed active seed cannot substitute for the revealed server seed. Inputs stay in this browser and are not added to the URL.
What this verifier does
It applies Stake’s documented HMAC generator and captured fairness mapping: the first four bytes become a value below one, which is scaled and floored to a displayed result from 0.00 to 100.00. It is labelled Reference because we have not matched it against a real disclosed Stake Dice round.
Check your roll in 4 steps
Rotate your seed pair on Stake to reveal the seed used for the bet.
Paste the revealed server seed, client seed and exact nonce. Include a saved pre-bet hash if you have it.
Press Replay Dice result.
Compare with your bet history. If the result differs, follow the replay mismatch checklist first. If it still differs, tell us with the disclosed inputs and game version. You do not need to place a new bet.
Evidence and scope
HMAC-SHA256 uses the UTF-8 server seed as key and clientSeed:nonce:0 as message. The first four bytes form a fraction below one. Stake’s game-events documentation describes the raw expression (float × 10001) / 100. Its captured fairness client applies the integer floor before dividing by 100, producing displayed values from 0.00 through 100.00.
Why Reference?
Our captures so far do not include a disclosed Stake Dice round, so we cannot yet compare this implementation with a real result. Until we can, the adapter stays Reference. You do not need to place a new bet to use it: revealed seeds from an existing compatible round can be checked.
The loadable example is synthetic. Its seed names explicitly say so, and its result is computed independently for regression testing. It is not a disclosed casino round or evidence of a pre-bet commitment. These examples do not qualify the adapter as Verified.
Captured client rules are separate from settlement
The public client uses a nominal 1% house edge and the formula 100 / chance × (1 − 0.01), displaying the multiplier to four decimal places. It accepts Below targets from 0.01 through 98.00 and Above targets from 2.00 through 99.99. These client observations do not certify successful server payouts, exact RTP or currency settlement. No Stake calculator, demo or simulator profile is enabled from this capture.
Sources: Stake’s RNG implementation, Dice game-events description and public fairness/client modules captured October 25, 2026. Raw network capture and account credentials are excluded.
FAQ
Can I use the active server-seed hash as the server seed?
No. The hash is a commitment, not the secret HMAC key. Entering the hash as a seed calculates a different sequence and cannot verify the hidden seed’s bets.
Does a matching synthetic example make Stake Verified?
No. It checks implementation consistency. Verified needs disclosed-round evidence and a prior commitment; neither is established by the supplied Stake Dice capture.
Are seeds sent to Stake or this site?
No. The reference form runs in this browser, without submitting seeds or adding them to the URL.