The Three Seeds
Most casino games ask you to take it on faith. Tower asks you to take it on math.
Every Tower outcome — where the mines are, on every row, of every game — is generated from independent pieces of randomness, combined with a keyed cryptographic hash. The pieces are committed before your bet and revealed after. If the math the operator showed you produced a different outcome than the one you saw, you would know.
This is what provably fair means.
The three pieces
Server seed — a random string generated by BitKong's game server. You do not see it before you play. You see a hash of it — a one-way scramble that proves BitKong has committed to a specific value without yet revealing what it is. After your session, the seed itself is revealed. You can hash it again and confirm it matches the hash BitKong published earlier.
Operator seed — a random string contributed by the gaming operator (or by BitKong itself on the demo). Independent of BitKong's server seed. Visible to you.
Client seed — a random string you choose. The default is random, but you can change it at any time. This is your contribution to the entropy. As long as you set it to anything BitKong cannot predict, the outcome cannot be pre-computed against you.
How they combine
The three seeds, plus a per-bet nonce, are fed into a keyed cryptographic hash from the SHA-256 family. The exact key, message, and delimiter format is defined by each integration's fairness specification — different operators may wire it slightly differently, but the principle is identical in all of them: a deterministic function maps fixed inputs to a fixed output, and nobody can compute or change the output without changing one of those inputs first.
The nonce is a per-bet counter. It guarantees that two bets with the same seeds produce different outcomes.
The hash output — a 256-bit number — is mapped, deterministically, into the game state: which cells in which rows are mines, in what order they would be revealed.
Once you know all the inputs, the output is fixed. There is no other path to it.
How to verify a game you played
After your session, the server seed is revealed. You now have all the inputs you need. The verification flow:
- Take the revealed server seed and hash it with SHA-256.
- Compare to the hash BitKong published before your session. They must match.
- Combine the seeds and nonce for the bet you want to check, in the order specified by the operator's fairness page (or BitKong's public docs).
- Apply HMAC-SHA-256 with the documented key/message split.
- Map the output to the Tower grid using the documented mine-placement function. The function is open. Read it if you want.
- The grid you compute should be identical to the grid you saw.
If it is not, BitKong cheated. It will not be.
Where to verify
A self-serve verifier with paste fields for your seeds is in development at /verify. Until it is live, the operator running the integration you played on can run the same check, and BitKong support can walk you through it directly. Reach us at hello@bitkong.com.
Why this matters
Most casino games have to be trusted. Most can be rigged in ways you would not notice. Provably-fair games are a different shape entirely — they are auditable by every player on every bet.
The math is the math.