Back to Obsidian Games

OBSIDIAN GAMES

Game fairness & verification

Obsidian Games publishes a commitment before a wager and reveals the server seed after settlement. A completed receipt records the inputs and result so they can be checked. Verification explains a result; it does not predict a future win.

Before and after a round

  1. The server creates a secret seed and commits its hash before accepting play.
  2. The wager records a client seed, unique round ID and the game settings. Shared Crash rounds use the client seed global.
  3. The game derives random draws from these inputs and applies its versioned rules.
  4. After settlement, the revealed seed can be hashed and the draws and outcome recomputed. An active Mines board or Blackjack shoe remains hidden until the round ends.

The current seed algorithm

The current protocol is RH2. Its commitment is the SHA-256 hash of RH2:seed: followed by the server seed. The 64-character hexadecimal seed is decoded into bytes and used as an HMAC-SHA-256 key.

For each draw, the message is the JSON array ["RH2", clientSeed, roundId, drawIndex, attempt]. The first 52 digest bits become the draw. Continuous draws divide that number by 2⁵²; discrete selections use rejection sampling before taking the remainder. The game rules map these draws to a roll, path, shoe, grid or reels.

How to verify a result

For house games, open Fairness receipts, enter the receipt ID and choose Recheck result. Shared Crash exposes Verify shared Crash round after the crash. Each slot has its own Game info or Rules & fairness panel with its commitment and completed receipt.

Compare the revealed seed with the commitment saved before play, then check the recorded client seed, round ID, game settings and rules version. The version matters: historical receipts retain their original rules even when new-round paytables change.

What verification does and does not establish

A matching receipt shows that its result follows the disclosed seed derivation and game rules. It does not constitute independent game certification, establish regulatory status, guarantee a particular return or verify that a withdrawal has been paid. Theoretical return is a long-run mathematical average; a session can lose its entire wagered balance.

Older RH1 receipts use a different derivation involving an EOS block. Their recorded protocol and verification controls identify them. Current RH2 play does not need that legacy block flow.

Report a mismatch

If a receipt fails verification, preserve its ID and error message. Do not repeatedly start new wagers to resolve it. Contact support with the game, time and receipt ID.