We do not ask you to trust us. Every Bink Originals outcome is built from seeds you can check yourself, so you can recompute any round and land on the same number we did. Games from outside studios run on the studio's own RNG and are not verifiable with Bink seeds.
Provably fair is a cryptographic system that lets you check a game outcome for yourself instead of taking our word for it. It covers Bink Originals, the games Bink builds and runs on its own servers. You recompute the result from the same inputs the server used, and the two numbers either match or they do not.
The system combines a server seed (our randomness), a client seed (your randomness), and a nonce (bet counter) through the HMAC-SHA256 cryptographic function. Neither party can predict or manipulate the outcome alone.
A step by step breakdown of the verification process.
Before your first bet on a seed pair, our server generates a random server seed and shows you its SHA-256 hash. The seed itself stays hidden for as long as that pair is active, so we cannot swap it after you bet.
You set your own client seed, or we generate one for you. It is yours to change whenever you have no round in play, and it is what stops us predicting an outcome on our own.
A nonce is an incrementing number that changes with each bet. Combined with both seeds, it ensures every single bet produces a unique, unpredictable result.
The result comes from HMAC-SHA256 keyed with the server seed, over the message clientSeed:nonce:hashIndex, where hashIndex starts at 0. The first 52 bits of the digest, divided by 2 to the power 52, give a number from 0 up to 1, and that number drives the game outcome.
Rotate your seed pair and the old server seed is revealed. From there you can confirm its SHA-256 matches the hash you were shown, and recompute every round you played on that pair. Rotating is the reveal: an active pair stays sealed so nobody can read ahead.
digest = HMAC-SHA256(key: serverSeed, message: clientSeed:nonce:hashIndex)
result = first 52 bits of digest / 2^52
hashIndex is 0 for a single value. Rounds that need more than eight random numbers step it up to pull a fresh digest, which is why it is part of the message you sign.
Provably fair covers Bink Originals, the games Bink builds and runs on its own servers. Games from outside studios run on the studio's servers and carry the studio's own certification instead. Here is exactly where the line sits.
All 17 in house games. Bink commits a hashed server seed before you bet and reveals the seed once you rotate the pair, so you can recompute the outcome yourself. The tool above reproduces 16 of them directly. For the rest, open the round from your bet details. Bink also builds slots of its own. Those are not Bink Originals and are not counted here, but they commit to the same seed pair, so a spin is seed verifiable the same way. Open it from your bet details.
Browse Bink OriginalsSlots, scratch offs, live dealer tables, Chaos rounds and PvP from outside studios (Hacksaw, Iconic21, BGaming and SPINA) are decided on the studio's own certified RNG servers. Those games never receive a Bink seed, Bink never generates or touches the outcome, and nothing on this page can verify them. Where a studio publishes a round replay or its own verifier, we link it from your bet details.
Separately from fairness, Bink publishes the return to player figure for all 17 Originals: 96.63% to 99.45%, with 14 of them at 98% or better. Provably fair shows a single round was not tampered with. RTP is the long run return of the game itself.
Want the full method, including the test vectors and what the system does not cover? The self audit writes every step down, and anyone can re run the checks. Read the self audit
Every game's result is derived from a server seed that's hashed and shown to you before the round begins. The answer is fixed before you commit.
Server seeds are committed via SHA-256 hash. We can't quietly swap a seed after the fact. The hash you saw at bet time has to match the seed we reveal.
You set the client seed, or roll a fresh one whenever you have no round in play. Without it, no outcome can be predicted, not by us and not by anyone watching the wire.
Rotate your seed pair and the server seed behind every round you played on it is published, next to the client seed and nonce you already had, so you can recompute each result yourself.
Use the recomputer on this page, or any HMAC-SHA256 library. Key it with the server seed, feed it clientSeed:nonce:0, take the first 52 bits of the digest and divide by 2 to the power 52. Trust is not required. The maths is the contract.
HMAC-SHA256 is not a casino invention. It is the same message authentication construction that TLS connections and signed API requests rely on.
Ready to play with mathematical proof of fairness?
Start PlayingBink Originals only. Studio games carry no Bink seed, so there is nothing here to recompute for them.