Nobody has to trust us. That is the design.
Every round of every game is a function of a seed the house committed to before the round, a seed the player chose, and a counter. Once the house seed is revealed, anyone can recompute the round with a few lines of code. The verifier below does exactly that, in your browser, for all eight games.
Before the round
The house generates 32 random bytes as its server seed and publishes their SHA-256. The player brings a client seed of their own and a nonce that counts rounds on the pair.
During the round
HMAC-SHA256(server seed, client seed:nonce:cursor) yields 32-bit words. Rejection sampling makes them unbiased for the range a game needs, and a Fisher–Yates shuffle turns them into tiles, cards or numbers. No other input exists.
After the reveal
Rotating the pair retires it and reveals the server seed. Hash it: it matches the commitment. Recompute the rounds: they match what was shown. Every bet-details view links here with its seeds filled in.
Shared rounds have no client seed
In Crash everybody plays the same round, so the player’s seed is replaced by a public one nobody can know in advance: a randomness beacon whose round is announced before bets close and published only after. Server seed hash before, beacon signature after, and the crash point falls out of the two. Pick Crash below and paste a round’s data.
The same scheme players already verify
This is the commit-reveal HMAC scheme the crypto-casino audience has checked for years, and our engine reproduces the public vectors of the widely used implementations bit for bit. Your players can use our verifier, their own, or a console snippet we hand out with every game.
Play a demo round, rotate the seed, then verify it here