THE QUICK ANSWER
Verification has two checks: the revealed seed must match the earlier commitment, and the game calculation must reproduce the recorded result.
01
Keep the commitment and the result together
Stake publishes a server-seed hash before play and keeps the original seed hidden while that pair is active. Its implementation says rotating the pair reveals the previous server seed.
Keep the completed bet reference and its original hash before changing the pair. A hash match checks the commitment; it does not replace recalculating the actual game result.
Two checks for one past result
Original hash
Save the pre-play commitment
Revealed server seed
Check it hashes to that commitment
Game calculation
Use the same client seed and nonce
Recorded result
Compare the output
Matching only the hash leaves the outcome calculation unchecked.
Original explanation · not an account screenshot02
Collect the inputs from the same completed record
Do not combine a current client seed with an old server seed from another pair. Retain punctuation and complete values when copying them.
| Original commitment | The server-seed hash shown for that seed pair |
|---|---|
| Revealed inputs | Server seed, client seed and exact nonce |
| Game | The matching game and its recorded result |
03
Use the published tools
- Once the game allows it, rotate the seed pair to reveal the prior server seed. Keep the revealed value with the old bet.
- Compare the revealed seed’s hash with the original commitment using Stake’s seed-check tool.
- Open the official Calculation page, choose the matching game and enter its client seed, server seed and nonce. Compare the generated result with the bet record.
Keep the inputs from one seed pair
Server seed
Revealed value for the old pair
Client seed
Value used by the selected bet
Nonce
Counter attached to that bet
Game and events
Correct conversion and any additional inputs
A mixed seed pair can produce a mismatch without proving a changed result.
Original explanation · not an account screenshot04
If the result does not match
Check the game selection, seed pair, nonce and any extra game-specific inputs. Stake’s implementation also documents a cursor for games needing multiple generated events; a generic three-field calculator is not a substitute for the matching game algorithm.
Save the inputs and mismatch for official support. Verification checks a past result against a published process. It does not make later results predictable, remove the house edge or establish that every third-party game uses this system.
BEFORE YOU CONTINUE
Quick checklist
- Keep the original committed hash.
- Use one completed bet and one seed pair.
- Check both the hash and calculated result.
- Use the matching game algorithm.
Official sources
Official help describes the feature. StrikePot’s checks explain how to read the account record and report a mismatch.
- Stake · Provably Fair Implementation · reviewed
- Stake · Provably Fair Calculation · reviewed
- Stake · Provably fair explanation · reviewed
Public documentation reviewed on 26 October 2026 (America/Toronto). No account login, claim, deposit, gameplay, withdrawal or recovery test was performed. Account controls and available options can change; follow the current official screen.
Need the details for a particular website?
The code directory records each partner’s code, referral method and offer status. Use the relevant partner page when your question also involves one of those details.
Partner pages may include affiliate links. A listing does not confirm a reward or account eligibility.
