What a valid verification does not establish
The mechanics are worth understanding precisely because they are limited. A short list of what remains outside the model is more useful than another explanation of the hashing, so here it is without hedging.
- Before playsha256(server seed)published as the commitment
- You chooseclient seedunder your control, editable
- Per roundhmac_sha256(seed, client + nonce)one digest per bet
- Mappingdigest to a number in rangeimplementation specific
- After rotationserver seed revealedhash must match the commitment
- 01
The paytable
A digest says which outcome was drawn, not how much it pays or how likely it was. The margin sits in the paytable and the probabilities, both of which are outside the hash entirely.
- 02
The mapping into a result
Turning a digest into a number in the game's range is a separate published step. It is implementation specific, and the commitment does not constrain it, so a verifier only means something when it follows that provider's recipe.
- 03
That your seed was the one used
Verification shows the revealed seed matches the commitment. Comparing it against the specific bet you are checking is a separate step, and one that requires the nonce or bet identifier for that round.
- 04
A complete history
If rotation is rare or no revealed-seed archive is published, you can only check the rounds you have material for. Coverage is a property of the operator's practice, not of the mathematics.
- 05
Client seed control in practice
If the client seed was generated for you, or changed after the bets, the operator could in principle have searched inputs before committing. The ability to set it yourself is what closes that route.
- 06
Everything outside the generator
Bonus terms, maximum-bet rules and abuse clauses operate independently of the hashing, and a bet whose digest verifies perfectly can still be voided under those terms.
Why the limits matter more than the mechanics
Mechanics are easy to describe and reassuring to read. Limits are the part that changes decisions. Knowing that a valid digest constrains the sampling and nothing else is what stops verification from being mistaken for evidence about value, and knowing that coverage depends on rotation is what stops a single successful check from standing in for an audit.
The practical upshot is a narrower and more accurate claim. If a result verifies against a published recipe, and your client seed was yours and set in advance, and the reveal covers the round you are checking, then the outcome was not chosen after your bet. That is worth having. It is also the whole of it, and any further conclusion about fairness or value is being drawn from something other than the check.
One more limit, about you
The model is a transparency tool, and transparency does not moderate play. If verification is being used to justify longer sessions, larger stakes, or extra rounds after losses, that is outside the scope of anything a digest can address. Deposit, loss and session limits, or a cooling-off period, are the tools aimed at that.
Disclosure: this page carries an affiliate link to gamdom.com/r/csgo2026. If you open an account through it we may earn a commission. It costs you nothing extra and it does not change what we write. 18+. Gambling involves risk and can cause serious financial harm. Provably fair is a transparency property, not an advantage: a verifiable result can still lose, and the house margin still applies.