FRFair Roll commitment · seeds · nonce · digest Partner site
Fair Roll / Checklist
Before you rely on it

Seven questions before you trust a verification

The list exists so you can decide in about a minute whether a particular implementation gives you anything checkable, instead of assuming that the phrase on the page means the arithmetic has been done for you.

  1. Before playsha256(server seed)published as the commitment
  2. You chooseclient seedunder your control, editable
  3. Per roundhmac_sha256(seed, client + nonce)one digest per bet
  4. Mappingdigest to a number in rangeimplementation specific
  5. After rotationserver seed revealedhash must match the commitment
  1. 01

    Was the commitment published before the first bet?

    Not alongside the reveal and not retroactively. If it cannot be shown to predate your play, the model grants nothing, however correct the arithmetic is.

  2. 02

    Can you set your own client seed?

    A client seed generated for you, from operator-chosen material, returns to the operator the freedom the model was designed to remove.

  3. 03

    Did you set it before the bets you are checking?

    Changing the client seed afterwards changes the digests. The value that matters is the one that stood when the bets were placed.

  4. 04

    Is the recipe published in enough detail?

    You need the exact message, the delimiters, which digest is used as the key and which part of the output is read. A description that says "HMAC-SHA-256" and stops there is not a recipe.

  5. 05

    How often is the server seed rotated and revealed?

    Rotation frequency sets how much you can ever check. A commitment that is never followed by a reveal leaves you with a promise rather than a verification.

  6. 06

    Can you get the nonce or bet identifier per round?

    Without a per-round identifier there is nothing to recompute, because the same seeds produce a different result for every nonce.

  7. 07

    Do you know what the check would and would not tell you?

    A pass means the outcome was generated from the committed seed as published. It says nothing about the paytable, the margin, or the next round.

Worth keeping if you check a result

  • The commitment text as published, saved with its date.
  • The revealed server seed and your client seed at the time.
  • The nonce or bet identifier, the amount and the timestamp.
  • The provider's published recipe, in the version you used.

Signs to stop and step away

  • Verifying hashes after a loss to decide whether to stake again.
  • Staking more because the last rounds verified.
  • Choosing games by whether they publish seeds at all.
  • Spending a session auditing instead of deciding whether to play.

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.