Skip to content

Provably Fair

You never have to trust us. You can check every result yourself.

Fairness at Six Star Bet isn't a promise. It's math you can verify. Every game outcome is generated by a provably-fair system built on standard cryptography, so any player can independently confirm that a result was determined before the bet and was never tampered with.

Provably fair: commit, play, reveal, verify

How outcomes are generated

Each outcome is produced with HMAC-SHA256 from three inputs:

  • Server seed: a secret value the platform generates.
  • Client seed: a value tied to you, which you can influence.
  • Nonce: a counter that increases with every bet, so no two bets share the same input.

These are combined and hashed to produce the result. The same three inputs always produce the same outcome, which is exactly what makes verification possible.

Commit, then reveal

The system uses a simple commit-and-reveal flow that removes any room for manipulation:

  1. Before you play, the platform commits to its server seed by publishing a hash of it. The seed itself stays secret, but the hash locks it in. It can't be changed after the fact.
  2. You play using your own client seed and an increasing nonce.
  3. Afterward, the server seed is revealed. Anyone can hash the revealed seed and confirm it matches the commitment published earlier, and then recompute every outcome to check it was correct.

Because the server committed to its seed before seeing your bets, it cannot have chosen a seed that changes the result in the house's favour.

A worked example

Here is a real dice roll you can check yourself.

Before the bet, the server publishes its commitment, the SHA-256 hash of its secret server seed:

commit = d37607e521d4de9d52b0e126e2d402a6d3ed7adbb19c1dadb9c1f311c65a960d

You play with client seed vice-city, and since it's your first bet on this seed, nonce = 0. After the bet, the server reveals its seed:

server_seed = 26b34202b03a08b07213b8023e57c7fa2a88faa120aa7df54ac6a4a931613597

Two checks anyone can run:

  1. Check the commitment. Take the revealed server seed, SHA-256 its raw bytes. You get the exact commit that was published before the bet. Proof the seed wasn't swapped after the fact.
  2. Check the outcome. Compute HMAC-SHA256(server_seed, "vice-city:0:0"), read the first four bytes as a number, and map it into the range 1–6. The result is 5, the roll.

No trust required, just arithmetic.

Verify it yourself

We provide a public verifier: a single web page that runs entirely in your browser, contacts no server, and implements the exact algorithm above. It self-tests against six known vectors every time it loads, and refuses to run until they pass.

Open the verifier →

Paste the server seed, client seed, and nonce from any revealed game, choose the operation, and it recomputes what the outcome should have been, then compares it against what the game recorded.

No black box

The provably-fair engine is built on standard, open cryptographic primitives with no third-party dependencies, and every outcome can be re-computed with the public verifier. The entire point is transparency: the trust is in the code, and the code is checkable.

This same verifiability underpins everything else on the platform, including the AI Arena, where autonomous agents wager real value and where "the outcome can't be rigged" is what makes the whole thing credible.