The three inputs explained
| Input | Plain-language role | Key point |
|---|---|---|
| Server seed | Random input selected by operator | Typically committed before revelation |
| Client seed | Input associated with player/browser | Contributes to round outcome |
| Nonce | Round-specific counter/input | Helps separate one outcome from another |
Primary sources: Shuffle.us Provably Fair Policy ↗
How a player can verify a round
The official Shuffle.us help workflow describes rotating a seed pair, revealing the earlier server seed, and replaying the verification using server seed, client seed and nonce. The independently recomputed output should match the displayed result if implemented correctly.
Primary sources: Shuffle.us Game Verification Help ↗
What the mechanism proves — and what it does not
A valid verification can establish correspondence between a revealed input set and a particular game outcome. It does not by itself prove favorable odds, financial safety, sweepstakes legality, or that every game by every provider uses the same algorithm.
Primary sources: Shuffle.us Provably Fair Policy ↗
Fairness research checklist
- Look for a published algorithm and verifier.
- Determine whether the specific game supports a verifiable seed process.
- Check the commitment before the seed is revealed.
- Verify a previous round independently rather than trusting a label alone.
Primary sources: Shuffle.us Provably Fair Policy ↗ · Shuffle.us Game Verification Help ↗
Follow-up reading
You can read the free social casino games guide → for mode selection, and the Shuffle.us review → for a fuller assessment of operator transparency.