Every round is checkable before it is played
Before your first bet the server committed to a secret seed by publishing its SHA-256 hash. It cannot
change that seed afterwards without the hash no longer matching. Your own client seed and a nonce that
rises by exactly one per bet go into the same calculation, so neither side can steer a result alone.
bytes = HMAC_SHA256(server seed, "client seed:nonce:cursor")
The cursor starts at 0 and steps up once per 32 bytes, which is how a round that needs more than 32
random bytes keeps going. Four bytes make one number in [0, 1). That is the whole scheme, and it is what
the verifier below reruns.
The server seed stays sealed while it is in play. Rotating your seed pair is what reveals it, and the old
commitment stays listed forever so you can check every round it produced.
Open the verifier ↗
— the SDK's own tool, shipped unchanged. Paste a revealed seed and its commitment to confirm they match.