Fairness you can recompute

The commit–reveal scheme

1. Before the round: the server generates a secret seed and publishes sha256(server_seed). The outcome is now fixed — the server cannot change it after seeing the bets.
2. During the round: players bet against the committed (still hidden) outcome.
3. After the round: the server reveals the seed. Anyone can check that sha256(server_seed) equals the pre-published hash, and recompute the result from the seed.

Verify without asking permission

The verification endpoint is public — no API key needed:

GET /api/v1/verify/<round_id>

It returns the round's revealed server seed, the committed hash, the client seed, nonce and the settled result. Recompute the hash locally; recompute the outcome; compare. If the platform ever altered a result after the fact, the hashes would not match — and that check is in your hands, not ours.

What this means for operators

Player disputes about "rigged rounds" become resolvable with arithmetic. Support can point at the verify endpoint; auditors can sample rounds independently; and the operator never has to take the provider's word for anything.