Every round can be replayed. Every number is stated.

• Before play, the server picks a secret server seed and shows its SHA-256 hash. That hash is a commitment: the seed can no longer be changed without the change being visible.
• The player sets a client seed of their own. Each round adds a nonce, a counter that goes up by one.
• The outcome is derived from HMAC-SHA256 of the server seed over the client seed and the nonce.
• When the player rotates seeds, the old server seed is revealed. Anyone can check that it matches the hash shown earlier and recompute every round played with it.

Some of our games are more than a single random number: they have movement, collisions and chains of events. We run them as a deterministic simulation. The same seeds and the same game version produce the same round, frame for frame, on our server and in the player’s browser.

The server result is the one that settles the bet. The browser shows exactly that result, not an animation picked to match it afterwards. Because a round is fully defined by its inputs, any round can be replayed later, by the player, by the operator or by an auditor.

Every game ships with a passport. It is written for operators and readable by players:

• Exact RTP, and how it was obtained: in closed form where the game allows it, otherwise by simulation, with the number of rounds and the confidence interval stated.
• The real maximum win: the largest multiplier the game can actually produce, and how rare it is, rather than a theoretical cap no round ever reaches.
• Hit frequency: how often a round returns anything at all.
• The shape of the payout distribution, so volatility is shown rather than described with a word.
• The game version the numbers belong to. A change to the maths is a new version with a new passport.

Crypto players check. A game whose rounds can be recomputed and whose numbers are written down is easier to list, easier to support and easier to defend in a dispute: the answer to a complaint is a replay, not an apology.