GO-STAKE site favicon
FEATUREDSTAKE ORIGINALS — DICE, PLINKO, MINES & CRASH
Independent affiliate review • Not owned or operated by Stake • Legal availability varies • Gambling involves financial risk • Affiliate disclosure
FAIRNESS · TECHNICAL EXPLAINER

Stake Provably Fair: Server Seed, Client Seed & Verification

Learn how Stake provably fair commitments use server seed, client seed, nonce and cursor, plus how to verify past rounds and understand limitations.

Independent affiliate information. 18+ or higher legal age. Access depends on jurisdiction. Gambling involves losses.

Step-by-step gambling-game guide image from the supplied archive
Editorial comparison, not Stake account support. Affiliate disclosure · Responsible gambling

What provably fair verification proves

Stake’s provably fair approach uses a commitment to a hidden server seed and publicly described calculations so eligible game outcomes can be checked later. Verification is about the integrity of the recorded result—not whether the wager was a good decision or would be profitable. Official fair source

Four inputs and their jobs

InputPurposeWhen it matters
Server seedOperator-generated secret later revealed after rotationHash commitment prevents silent after-the-fact substitution
Client seedPlayer-controllable contributionChanges the deterministic input sequence
NonceCounter progressing across betsSeparates results within a seed pair
CursorPosition within generated byte streamSupports games needing multiple output bytes

Stake documents HMAC-SHA256 generation from the server seed and client-seed/nonce/cursor sequence. Game-specific conversion logic is required to turn the bytes into the visible result. Official impl source

How to verify an earlier game result

  • Record the original displayed hash of the server seed and the client seed used for the round.
  • Find the completed bet’s nonce and any game-specific inputs.
  • Rotate or reveal the old server seed using the operator’s documented process.
  • Hash the revealed seed and compare the hash with the earlier commitment.
  • Reproduce the game’s documented output calculation and compare the resulting game outcome.

If the documented result cannot be reproduced, double-check the game version, nonce, cursor and other inputs; a mismatch is not automatically proof of fraud. Stake provides an implementation guide and server-seed unhash utility. Official impl source

Why server seed rotation matters

Before the server seed is revealed, knowing its hash does not allow straightforward prediction of the next result. Revealing the seed after rotation permits historical checking while a new hidden seed is used for future outcomes. Stake explains this reveal-and-replace model in its official implementation. Official impl source

Limits of the fairness label

  • A mathematically verified losing result is still a loss.
  • Provably fair verification does not remove the house edge or guarantee an RTP over a short session.
  • Verification does not independently confirm the operator’s license, location permission or payment reliability.
  • Third-party provider slots or live dealer games may use different fairness controls.

The broader casino review explains provider categories, and our game mechanics comparison provides a probability example. Official blog source

Primary sources and review scope

Official product information checked 16 November 2026. Operator terms, games and available regions may change. The official sources below support the specific claims above; GO-STAKE is not Stake.com.

Independent player safety information · Self exclusion resources