Provably fair
How it works
MP5.GG commits to every result before you play. You can check each one later, with the published formulas and the open-source verifier.
Games
Seeds and nonces
Before you play, MP5.GG shows the SHA-256 hash of a secret server seed: 32 random bytes written as 64 lowercase hex characters. Your browser then picks the client seed (you can type your own), and each bet uses the next nonce, from 0. Rotating reveals the server seed, so you can recompute every bet it was used for, and the next seed, whose hash you saw in advance, takes over.
A client seed is 1 to 64 printable ASCII characters without a colon, so your browser and the server encode it identically. The server never starts a seed pair without a client seed from your browser or from you.
The byte stream
Block c of your stream is an HMAC-SHA256, keyed by the server seed's 64 hex characters:
HMAC-SHA256(serverSeed, "mp5gg:v1:{game}:{clientSeed}:{nonce}:{c}")The blocks are read in order as big-endian 32-bit words. This is fairness version 1: a change to any rule here would be a new version, and bets made under version 1 keep verifying under it.
Integer draws
Every number is a whole number drawn without bias. uniformInt(n) takes the next word w; if w is at or above floor(2^32 / n) × n it is discarded and the next word read, otherwise the result is w mod n. Ranges past 2^32 read as many words as they need the same way (uniformBig).
Positions, seats, rounds and cells count from 0 in the formulas and from 1 on screen. Animations never use the stream: the reel's filler and where it stops are cosmetic.
Battles and the public beacon
A battle's server seed is committed when the battle is created. When the last seat fills, MP5.GG announces a future EOS block: the projected head plus 3 blocks, about 1.5 seconds ahead, with the providers that will report it. The announcement never changes.
The battle settles once two independent providers report that block irreversible with the same id, produced after the fill. The verifier asks its own providers (4 by default, plus any you add), never the ones the battle named. If no provider returns the block within 24 hours, every seat is refunded once, and the would-be result is published when the block appears.
The verifier is the same code the server settles with. It is published as an open-source package with its test vectors.