Capture what existed before play.
Record the commitment shown before the player action. The review should make clear which value was fixed and when it became visible.
Round verification
Do not take fairness on trust.
Reproduce the round.
A verifiable flow connects the commitment made before play with the round inputs, revealed value and documented calculation used to produce the result.
Verification sequence
Follow one round from commitment to result.
The exact fields depend on the game format, but the sequence should remain understandable and repeatable.
Preserve the complete round context.
Keep the player-controlled input, nonce or round counter, selected game parameters and the identifier that connects the evidence to the round.
Resolve the earlier commitment.
After reveal, confirm that the disclosed value matches the pre-play commitment before using it to calculate an outcome.
Run the documented calculation.
Use the disclosed inputs and algorithm to reproduce the raw result, then follow the game-specific mapping into the visible outcome.
Match evidence to settlement.
Check that the recomputed result, displayed result and wallet settlement refer to the same round and configuration.
Make disputes reviewable later.
Define how long round evidence remains available, how access works and what happens when a record cannot be reconstructed.
Operational verification
Test the explanation as well as the math.
A correct calculation is useful only when it can be tied to the round the player saw and retrieved later by support. Use a sandbox example, save its inputs and reproduce it from the documentation alone.
Each game family may add a multiplier curve, board path, reel evaluation or timed state to the common commitment flow. Document those format-specific steps alongside the shared verification method.
- Can you prove the commitment preceded the player action?
- Are all required inputs and transformations documented?
- Does recomputation reach the same visible and settled outcome?
- Can support retrieve the data using the round identifier?
- Are missing, expired and mismatched records handled explicitly?
Round verification is one part of the broader game testing process. Wallet, retry, limit and operational behaviour still need separate tests.