Every round is committed before betting opens and is identical for every
player in that room. The room draws a secret server seed, then publishes
a SHA-256 commitment binding it to the public client seed,
round number and RNG version. After the race settles, the server seed
is revealed so your browser can reconstruct the commitment and compare
it with the one it observed before the result.
The result comes from the round digest:
HMAC-SHA256, keyed by the revealed server seed, over the round's
message string. The winner is mapped from that digest. Your browser
reconstructs the canonical messages for the round's RNG version and
checks the commitment, digest, winner and complete finishing order.
Server seed (SHA-256 commit)
—
Server seed (revealed)
—
Client seed (public)
—
Round (nonce)
—
Round digest
—
Result winner
—
The server determines the outcome; camera movement and animation do
not affect it. Verification detects a reveal that differs from the
commitment your browser observed. Joining after the result can verify
internal consistency, but not that the commitment was published earlier.
These checks do not independently certify how the server generated its
secret seed.
