1. Overview
The outcome of every round is derived from a HMAC-SHA256 hash of a committed server seed, a client seed you influence, and a monotonic nonce. Because the server seed is committed (published as a hash) before the round begins, we cannot change the outcome after the fact.
2. Lifecycle
- Server generates a random 256-bit server seed and publishes its SHA-256 hash to your session ('the commitment').
- You may set or randomise a client seed. If you do not, the client generates one for you.
- Each round increments a nonce.
- The engine computes HMAC-SHA256(server_seed, client_seed:nonce) and derives cards from the bytes.
- When you rotate the seed, the previous server seed is revealed. You can then verify that its SHA-256 matches the earlier commitment and reproduce every round independently.
3. Reshuffling
Tables may be configured to reshuffle every hand, on penetration, or after a burn count, per the table settings shown in the lobby. Reshuffle events are deterministic against the committed seed and are logged with the round.
4. Independent Verification
We publish a verifier tool that accepts the revealed server seed, client seed, and nonce range, and reproduces the exact card sequence for those rounds. The algorithm is documented and open for inspection.
5. Void Rounds
Rounds may be voided and ledger entries reversed where a round is affected by verifiable engine malfunction, latency exploitation, collusion, or a bug. Void decisions are logged, disclosed to affected players, and subject to the dispute process (Disputes).
6. RNG Assurance
Where required by local regulation, our RNG and game engine are subject to independent testing by an accredited testing laboratory. Certificates and reports are made available to regulators on request.
7. House Rules
Each table clearly displays the applicable rules — deck count, dealer S17/H17, double after split, resplit aces, surrender availability, insurance payout, blackjack payout (3:2 or 6:5), and any variant such as Switch or Free Bet. Rules are enforced identically by the engine and by the UI action gating.
8. Contact
Fairness questions: fairness@tethbet.com.