Have you ever wondered whether the games you play are genuinely fair? Provably fair gaming is a cryptographic method that lets you verify, independently and after the fact, that a result was fixed before you placed your bet — and that nobody changed it afterwards.
This guide walks through how to check a result yourself, step by step, with a fully worked example you can reproduce on your own machine in under a minute. No programming required.
Provably fair systems commit to a secret server seed by publishing its SHA-256 hash before you play. Your own client seed and an incrementing nonce are combined with that seed to produce each result. Afterwards the server seed is revealed, you confirm it hashes to the published commitment, and you re-derive the outcome yourself. If both match, the result could not have been altered.
Which SpinSaga Product This Applies To
SpinSaga runs two platforms, and they use different fairness models.
The crypto casino is where provably fair verification applies. Seeds are exposed per round, you can set your own client seed, and results can be re-derived independently.
The social casino uses the model standard across sweepstakes platforms: games come from third-party studios whose random number generators are independently tested and certified. You cannot re-derive an individual spin, because the provider does not publish per-round seeds — but the generator itself is audited. Our explainer on how RNG ensures fair gameplay in social casinos covers how that testing works, and whether SpinSaga is legit covers the wider trust picture.
Neither model is weaker. They answer the same question — was this result manipulated? — with different evidence. Provably fair gives you a proof you can run yourself. Certification gives you an independent lab's verdict on the generator.
What You Need Before Starting
The server seed hash — a cryptographic fingerprint published before you play.
The server seed itself — revealed after you rotate seeds or after a set number of bets.
Your client seed — a string you control and can change.
The nonce — a counter incrementing with each bet on the current seed pair. Some implementations start at 0, others at 1.
A SHA-256 hash tool. Any browser-based generator works. On macOS or Linux,
shasum -a 256andsha256sumare already installed.
No advanced skills needed — just precision with copy and paste.
Step-by-Step Guide
Step 1: Locate the Server Seed Hash and Server Seed
After a bet, open your bet history or the fairness section. You will see the server seed hash — a 64-character hex string. It was generated before your bet and is the hashed form of a seed still being kept secret.
The seed itself is revealed when you rotate it, or after a set number of bets. Copy both exactly. A single missing character changes the hash completely.
💡 Pro Tip: Rotate your server seed deliberately when you want to verify a batch of results. Rotation is what releases the old seed for checking.
Step 2: Set or Retrieve Your Client Seed
Your client seed is a string you control, and it is the part that stops the operator predicting outcomes in advance. Set your own in the fairness settings, or note the default currently in use.
The important detail: the client seed must be in place before the bets you intend to verify. Verifying an old bet means retrieving the client seed that was active at the time, not the one you are using now.
💡 Pro Tip: Use a random string, not personal information. Your name or birthdate works cryptographically but ends up stored alongside your betting history.
Step 3: Obtain the Nonce
The nonce increments with each bet placed on the current server seed, so the same seed pair produces a different result every round. Find it beside each wager in your history. Rotating the server seed resets it.
💡 Pro Tip: If you plan to verify several results, note the nonce alongside each one as you go. Reconstructing which bet was which afterwards is the fiddliest part of the process.
Step 4: Verify the Server Seed Against Its Hash
Run SHA-256 on the revealed server seed and compare the output to the hash published before your bet.
printf '%s' "YOUR_SERVER_SEED" | sha256sum
On macOS, use shasum -a 256 instead. Use printf rather than echo, because echo appends a newline that changes the hash.
If they match, the operator committed to that seed in advance and could not have swapped it after seeing your bets. This single step is the heart of the whole system.
💡 Pro Tip: A mismatch is almost always a copy error — a trailing space, a truncated string, a newline. Re-check your input carefully before concluding anything about the game.
Step 5: Re-derive the Game Outcome
Combine the three inputs and hash the result. The most common format is server_seed:client_seed:nonce, though the exact construction varies between operators and games, so check the fairness documentation for the specific title.
The resulting hash is then converted into a number. One widespread method takes the first 8 hex characters, converts to decimal, and divides by 2³² to produce a value between 0 and 1.
💡 Pro Tip: Many operators provide a built-in verifier that does this automatically. Running it manually once is still worthwhile — it tells you the verifier itself is honest.
Real Example You Can Reproduce
Every value below was computed with SHA-256. Run the commands yourself and you will get identical output — that is the point of the exercise.
The inputs:
Field | Value |
|---|---|
Server seed |
|
Published hash |
|
Client seed |
|
Nonce |
|
Step one — confirm the commitment.
printf '%s' '8f2a9c4e7b1d3a6f5e8c2b9d4a7f1e3c6b8d2a5f9e1c4b7d3a6f8e2c5b9d1a4f' | sha256sum
Output: 95b2ac94b7102657acadbef392040b0ccaa15884689a5f3e5d5f2624e0143c77
That matches the hash published before the bet. The seed is confirmed.
Step two — re-derive the result.
printf '%s' '8f2a9c4e7b1d3a6f5e8c2b9d4a7f1e3c6b8d2a5f9e1c4b7d3a6f8e2c5b9d1a4f:myrandomseed123:1' | sha256sum
Output: eb0695fdd62898ec0f796d8d24a1b0c2d1dd6e6485d8d62cb37f9b28f16f99d9
Step three — convert to a number.
First 8 hex characters:
eb0695fdAs decimal: 3,943,077,373
Divided by 2³² (4,294,967,296): 0.91807
Expressed on a 0–100 scale: 91.81
Watch the nonce work. Same seeds, next bet:
Nonce | First 8 chars | Roll |
|---|---|---|
1 |
| 91.81 |
2 |
| 70.45 |
3 |
| 35.35 |
Three completely unrelated results from identical seeds. That is the nonce doing its job, and it is why one seed pair can safely cover hundreds of rounds.
One honest caveat about slots. A single 0–100 roll maps cleanly onto dice, crash and similar games. A slot needs many random draws per spin — one per reel position, plus more for features — so verifying a slot means following that game's documented derivation, which will produce a sequence rather than one number. The principle is identical; the arithmetic is longer.
How to Choose Your Verification Method
Occasional checks: use the operator's built-in verifier. Fastest route, and fine for spot checks.
Full independence: hash locally with sha256sum or shasum. Nothing leaves your machine and you are not trusting a third-party website with your seeds.
Frequent verification: a short script will automate it, but only go this route if you are comfortable writing one.
Whichever you pick, favour platforms that publish the hash before play, let you set your own client seed, and reveal server seeds on rotation. Missing any of those three and the system is not doing what it claims.
Why It Works
Provably fair rests on cryptographic commitment.
Before you bet, the operator generates a random server seed and publishes its hash. SHA-256 is a one-way function: trivial to compute forwards, computationally infeasible to reverse or to find a second input producing the same output. So the published hash pins the operator to that exact seed without revealing it.
Afterwards, the seed is revealed. You confirm it hashes to the published commitment — proving it is the original seed, not a substitute chosen once the operator saw your bets. Then you combine it with your client seed and the nonce to re-derive the outcome.
Your client seed is what closes the loop. Because you chose it and the operator committed to the server seed before seeing it, neither side could steer the result. That is the whole proof, and it is why the ordering matters: a client seed set after the fact proves nothing.
What provably fair does not do is change the house edge. It proves the result was honestly derived, not that the game is generous. A verifiable 96% RTP game still returns 96% — see volatility vs RTP when choosing a slot for what those numbers actually mean, and how progressive jackpot slots work for how large prizes are funded.
Common Mistakes
Copying the seed incorrectly. One missing character, one trailing space, one line break and the hash changes entirely. Always copy and paste.
Using echo instead of printf. echo adds a newline by default, which is part of the hashed input and will give you the wrong answer. Use printf '%s', or echo -n.
Using the wrong nonce. It must match the exact bet. Off by one and you get a valid-looking hash for a different round.
Verifying with a client seed set afterwards. The client seed has to predate the bets it covers. Changing it and then verifying older rounds proves nothing.
Assuming a mismatch means manipulation. It nearly always means a transcription error. Re-check every input before drawing conclusions — and if it still fails, contact support with your exact inputs.
Applying the wrong conversion. Different games derive outcomes differently. Read that game's fairness documentation rather than assuming the first-8-characters method.
FAQ
What is provably fair gaming?
A system using cryptography to let players verify that outcomes were fixed before betting and not manipulated afterwards. It works by publishing a hashed server seed in advance and revealing the seed later for checking.
Do I need technical skills?
No. You need to copy and paste accurately and run a hash tool. Most operators also provide one-click verification.
Can I verify results on SpinSaga?
Provably fair verification applies to the crypto casino. On the social casino, fairness is assured through independently tested and certified RNGs rather than per-round seed verification — see how RNG ensures fair gameplay.
What if the hash does not match?
Almost certainly a transcription error. Re-check the seed, the client seed, the nonce, and whether a stray newline crept in. If it still fails after careful re-checking, raise it with support and include your exact inputs.
How often should I verify?
As often as you like. Most people check once to satisfy themselves the system works, then occasionally after a notable result.
Is provably fair gaming legal?
The technology itself is a transparency measure, not a regulated activity. What matters is whether the platform you are using is licensed and permitted where you live.
What is a client seed and why does it matter?
A string you control that is mixed into every result. Because you choose it and the operator has already committed to the server seed, neither party can steer the outcome. Without it, the commitment alone would not be enough.
Does provably fair mean better odds?
No. It proves the result was derived honestly. The house edge and RTP are unchanged — a provably fair game with a 4% edge still has a 4% edge, you can simply confirm it was applied correctly.
Play With Confidence
Verification is a habit worth having once. Run it a single time on a real result and the system stops being a marketing phrase and becomes something you have personally checked.
If you play SpinSaga's social casino instead, the fairness question is answered differently but just as seriously — through independently certified random number generators. Start with how RNG ensures fair gameplay, whether SpinSaga is legit, and why SpinSaga is a favorite among social gaming fans.
New to the social casino? You play with Gold Coins for entertainment and Saga Coins as sweepstakes entries, with no purchase necessary to play or win. New players receive 100,000 GC and 5 SC, and everyone collects a full Saga Coin daily. Saga Coins can be redeemed for prizes — the withdrawal guide covers the process, the sweeps rules the conditions, and the state-by-state overview where it is available.
Sign up today, or browse the SpinSaga blog for more guides.
Play SpinSaga Now — Get 100,000 GC + 5 SC Free!
Disclaimer: Free-to-play social casino. No purchase necessary to play or win. Must be 18+ (or the minimum legal age in your jurisdiction). Void where prohibited. Please play responsibly. Bonus figures are accurate as of 2025 and subject to change — see the terms and conditions and privacy policy for current terms.