Verify any round yourself
You do not have to take our word for a result. Enter any past round below to see the hash we published before betting opened, the seed we published after the draw, and the digits derived from it.
How it works
- Every round has a secret seed, derived from a private master key and the round number.
- Its SHA-256 hash, the commitment, is shown on the live round panel before betting opens. The hash gives nothing away.
- Bets are accepted. The commitment is already public and cannot be changed.
- At draw time the result is derived from the seed by the published method below.
- The seed is revealed. Hash it, compare it to the commitment, and you have your proof.
Reproduce a Win Go digit yourself
- Take the round index the verifier shows. It is the round’s start time in milliseconds divided by the round length, and the issue number encodes the same start time.
- Check the seed: SHA-256 of the 64-character seed, hashed as text, must equal the commitment that was shown before the round opened.
- For the digit, compute HMAC-SHA256 with the seed (as text) as the key and the message "<roundIndex>:d" followed by ":0".
- Read the result as eight 32-bit numbers, 8 hex characters each. The first one below 4,294,967,290 gives the value as that number mod 10. In the rare case none is below it, repeat with ":1", then ":2".
K3 and 5D use the same method with one message per die or position: "<roundIndex>:dice0" to "dice2" (each value mod 6, plus 1) and "<roundIndex>:pos0" to "pos4" (each value mod 10).
Reproduce a Aviator crash point
- Check the seed: SHA-256 of the 64-character seed, hashed as text, must equal the round’s commitment.
- Compute HMAC-SHA256(key = seed, message = "bust"). If its first 8 hex characters, read as a number, divide evenly by 40, the round crashed at 1.00×.
- Otherwise compute HMAC-SHA256(key = seed, message = "point") and read its first 13 hex characters as a number h.
- The crash point is floor((100 × 2^52 − h) ÷ (2^52 − h)) ÷ 100, capped at 100×.
Frequently asked questions
What is a commitment?
The SHA-256 hash of the round’s secret server seed, shown on the live round panel before betting opens. A hash cannot be reversed, so it reveals nothing about the result, but it locks the seed in, because any other seed would produce a different hash.
Why is the seed only shown after the draw?
Because anyone holding the seed can compute the result. Revealing it early would let a player bet on a known outcome. It is published the moment the round settles, or for Aviator the moment the round crashes.
How do I verify a round myself?
Enter the room and issue number above to get the round index, the commitment and the revealed seed. Hash the seed with any SHA-256 tool and check it matches the commitment. Then follow the step-by-step method below to reproduce the result with any HMAC-SHA256 tool.
Are the seeds random?
Seeds are not random draws: each is derived from a private master key and the round number, so they are fixed in advance and cannot be steered by where bets went. A commitment proves the result was fixed before betting only if you note it before the round opens; it is shown on the live round panel for exactly that reason.
What this does not prove
Verifiable draws mean results were not manipulated. They do not remove the house edge, which is published as RTP on every game page and is how the platform earns regardless of any individual round. Both things are true at once, and we would rather say so than let the word "fair" do work it cannot.