Rotate to portrait
Bink is designed for portrait mode.
We don't ask you to trust us. Every game outcome is cryptographically verifiable. You can independently prove that no result was tampered with.
Provably fair is a cryptographic system that lets you verify the fairness of every single game outcome. Unlike traditional casinos where you must trust that the games are fair, provably fair gaming uses mathematical proof.
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 each bet, our server generates a random seed and gives you its SHA-256 hash. The seed itself stays hidden until the round is over, so we cannot change it after you bet.
You provide your own client seed, or we generate one for you. This seed is fully in your control and can be changed at any time. It ensures we cannot predict the outcome alone.
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 final result is generated using HMAC-SHA256(serverSeed, clientSeed:nonce). This cryptographic function produces a deterministic but unpredictable output that determines the game outcome.
After each bet, the server seed is revealed. You can independently verify that the hash matches and recalculate the result using our verification tool or any HMAC-SHA256 calculator.
result = HMAC-SHA256(serverSeed, clientSeed:nonce)
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 any time. Without it, no outcome can be predicted, not by us and not by anyone watching the wire.
Server seed, client seed, and nonce are all published the moment the round closes, so you can recompute the result yourself.
Use the verifier on this page or any HMAC-SHA256 calculator on earth. Trust isn't required. The math is the contract.
HMAC-SHA256 isn't a casino invention. It's the same construction banks, certificate authorities, and TLS connections rely on for message integrity.
Ready to play with mathematical proof of fairness?