Provably-fair gaming only works if the server seed actually rotates. A casino that never rotates can be audited once — but if you want to spot-check rounds you played last month, the seed has to have been revealed. Bink.bet documents its rotation cadence, makes rotation player-triggerable, and reveals the previous server seed the moment you rotate. What that reveal lets you check is written out below, step by step, and you can export the whole history as a signed file.
The provably-fair commit/reveal flow (explained in full here) only finalizes when the server seed is revealed. Until then, you can verify that the commitment hash hasn't changed, but you can't verify any individual round's outcome.
A rotation reveals the active seed and commits a fresh one. The reveal is what lets you spot-check every round you played under that seed. So the answer to "how often does Bink rotate" is "exactly when you want it to."
| Trigger | Cadence | Notes |
|---|---|---|
| Player-initiated rotation | On demand, any time | Open any Bink Original, tap Fairness in the game footer, and use the Seeds tab. Rotating reveals the current server seed (so every prior round can be verified) and commits a fresh seed for the next round onwards. |
| First seed pair | On first use | Bink generates your first pair the first time one is needed — your first Bink Originals round, or the first time you open the Fairness panel, whichever comes first. Creating it commits the server-seed hash you can read from that moment on. |
| Nonce ceiling | At 2,147,000,000 rounds on one pair | The nonce is a 32-bit integer. A pair that reaches 2,147,000,000 rounds stops accepting bets and tells you to rotate, rather than failing inside the bet itself. This is the only rotation Bink forces, and it forces you to press the button — Bink never rotates your pair for you. |
| Nonce reset | Always, on rotation | One nonce per seed pair, shared across every Original — it increments by 1 each round you start, whichever game you start it in, and resets to 0 against the new server seed when you rotate. It is automatic and cannot be skipped. |
| Algorithm version change | Versioned (rare) | Every round records the derivation version it was played under, so a change to the algorithm does not strand the rounds behind it — each one still replays under the rule that settled it. Bink has shipped one such change, from v1 to v2, and it did not rotate anybody's seed pair. |
/games/<game>/verify handles the arithmetic automatically.Rotating reveals the server seed that was active, in the same operation that commits the next one. With it you hold everything a verification needs:
Those four inputs re-derive any round in the window, on this site's verifier or on your own machine against the published algorithm.
You don't have to copy those four inputs down by hand. In the same Fairness → Seeds panel, Download Signed Export saves a JSON file containing:
The file is signed with Bink's Ed25519 key, and it is signed for real — the exact bytes covered by the signature are inside the file, so there is nothing for you to reassemble. The public key is at /api/v1/games/seeds/export/public-key, and each export carries the one-line command to check itself. If the signature verifies, Bink issued that file and nobody has edited a number in it since.
Two limits worth knowing before you click. It covers Bink Originals only— studio and provider games run on the studio's own RNG, have no Bink seed pair, and are absent from the file rather than silently counted as verified. And it comes a page at a time, up to 100 rounds per file, because each file is signed over its own contents: stitching pages together would produce a document the signature no longer covers. The panel tells you when older rounds are still waiting.
Bink's provably-fair source code lives in packages/crypto-utils/src/games/. See /provably-fair for the algorithm overview and the live verifier. Operated by Bink Entertainment LLC (UEI RJXQZDNFMGV6).