Get Provably-Fair State

Returns the server seed hash, client seed and nonce that the player's next bet will use. FE calls it to show the provably-fair panel before the player bets.

Auth: Player session — Authorization: Bearer {token}
Rate limit: 300 requests per 60 s per IP (GAME_GET_PROVABLY_FAIR)
Games: THAI-HILO, LOTTO

How it works

THAI-HILO single-player (SINGLE rooms, POST /g/thai-hilo/bet): each player has one state per game and per demo/real mode — a secret server seed (64-character lower-case hex), its hash, a client seed and a nonce. It is created on the first provably-fair call or bet with clientSeed "default" and nonce 1.

Commitment: serverSeedHash = lower-case hex SHA-256 of the server seed text. Show it before the player bets; the active server seed itself is never returned.

Client seed: POST /provably-fair/client-seed replaces the client seed and resets the nonce to 0; the server seed and its hash do not change.

Nonce: each single-player bet uses the current nonce, then the nonce goes up by 1.

Roll: bytes = HMAC-SHA256(key = the server seed as text — the 64 hex characters as-is, NOT hex-decoded; message = clientSeed + ":" + nonce in decimal). Die i (i = 0, 1, 2) = floor(uint32 big-endian of bytes[4i..4i+3] / 2^32 × 6) + 1.

Rotation: POST /provably-fair/rotate reveals the current server seed (revealedServerSeed with oldServerSeedHash), replaces it with a new one and resets the nonce to 1; the client seed is kept. Bets made under a seed can only be verified after that seed has been rotated out. GET /provably-fair/server-seed returns a rotated-out seed again by its hash.

Verify: POST /provably-fair/verify-result recomputes from what FE sends (serverSeed, clientSeed, nonce) and returns the dice and the SHA-256 of the seed. FE checks the hash equals the commitment shown before the bets and the dice equal the recorded roll; nothing is looked up on the server.

LOTTO, and THAI-HILO MULTI / MULTI_CSEED rooms, have no per-player server seed: each round publishes its own seedHash when it opens and reveals the seed at settlement. A MULTI round seed is the text "{brand}{gameCode}{roomID}{unixNano}{result}_{64-hex nonce}" (the drawn result is embedded; hash = SHA-256 of that text). A MULTI_CSEED round seed combines the room server seed with the round's client-seed slots.

In MULTI_CSEED rooms of both games, the player's clientSeed and nonce are what a bet contributes when it claims a client-seed slot.

Rules

THAI-HILO: serverSeedHash is the player's own current commitment for single-player bets; the state is created on the first call.

LOTTO: serverSeedHash is the seed hash of the open (betting or rolling) round of one active room that serves the session currency — not necessarily the room the player is in. For a specific room use the room round calls.

LOTTO answers 404 99941 between rounds (no open round) and 404 99934 when no active room serves the currency.

LOTTO always uses the session currency; there is no currency parameter.

clientSeed is "default" until the player sets one.

nonce — THAI-HILO: the nonce the next single-player bet will use (1 on a new or rotated seed, 0 right after a client-seed change). LOTTO: the nonce a MULTI_CSEED bet contributes.

Demo and real play keep separate states.

Flow

Validates the token, checks system maintenance and resolves gameCode.

THAI-HILO: loads the player's state, creating it on first access (new server seed, clientSeed "default", nonce 1), and returns its hash, clientSeed and nonce.

LOTTO: checks the game is active, takes the first active room for the session currency and its open round, and returns that round's seed hash with the player's clientSeed and nonce.

Request

Responses