Verification

How to verify a round yourself

Your browser checks the secret of any round against the fingerprint recorded before the bet and recomputes the round number, usually in under a minute.

Verify a round on this page

Where to get the signature: after a round, the “Verify this round” link under the game's button opens this page with the round already filled in; the rounds in your account history have the same link. Any round will do, your own or someone else's: all transactions are public.

Paste the signature of the settlement transaction or a link to it from an explorer. The site will request the transaction from a network node, decode the outcome and recompute in your browser that the revealed secret matches the root recorded before the bet and that the prizes follow from the round number.

The same round in a Solana explorer
  1. After a round, an “explorer” link stands next to “Verify this round” under the game's button. It opens the settlement transaction in the explorer.
  2. Another way: open your wallet address in an explorer. The list shows the transactions it signed: top-ups, withdrawals and bets. The settlement is sent by the house with a different signature, so it is more reliable to open it via the link from the game.
  3. In the settlement transaction, open the program log (Program Logs). The outcome is recorded there as an event in encoded form (the “Program data” line); it can be decoded by any tool that understands the contract's interface description (IDL).
  4. Even without decoding, two things are visible: which program was called and that the settlement was made after the bet. Check the credited amount against the change in your game balance and against the prize table on the game's page.
Two transactions and one check
  1. The houseBefore the betThe fingerprint of the round secret is recorded in the contract.
  2. YouYour betIt lands in a Solana block that does not exist yet, so nobody knows its hash.
  3. ContractSettlementThe secret is revealed. The contract checks it against the fingerprint and computes the result from both parts.

After settlement anyone can recompute the round in a browser.

  1. Bet (spin_commit). Sent by your wallet or by the session key. It shows the round size and the game number, and in the player account the contract records the number of the round secret and the secrets root in force at the moment of the bet.
  2. Settlement (spin_settle). Sent by the house. The transaction log has three events: RoundRevealed with the secret number, the root, the secret itself and the hash of the bet's block; RoundInputs with everything else the result depends on: the game, the round size, the prize cap and the state of the pots; SpinSettled with the round's outcome: the prize total, the number of repeat spins, and whether there were jackpots.
  3. Check. The revealed secret must match the root recorded before the bet: this means the house did not substitute it after the bet. The contract itself performs this check at every settlement and will not accept any other secret; anyone can repeat it.

For those who want to recompute it themselves. The round secret, the root and the hash of the bet's block are published in the events of the settlement transaction. All hashes are computed with SHA-256, and the result must equal the root from the contract.

The “hash of the bet's block” is the value the Solana network recorded for the bet's slot in its SlotHashes list (the slot's bank hash). It is not the “blockhash” field an explorer shows for a block, so the two differ. The program reads the value from the network's own SlotHashes account (SysvarS1otHashes111111111111111111111111111) and takes none from the sender; any node returns that account, and it keeps a slot for about 3.5 minutes.

What verification proves

That the round number was obtained by the rule: from a secret fixed by its fingerprint in the contract before the bet and the hash of the bet's block. And that the prizes follow from that number: the page recomputes them from the inputs published in the same transaction and compares them with what the contract credited. For a round settled before the program began to publish these inputs, the prize is read from the settlement event. Verification does not promise a win. More on how it is built: “Contract”.

What else you can verify

The size of the pots

The prize bank and the jackpots on the site are numbers from the shared game account in the contract. The same account can be opened in the explorer.

The administrator's share

The administrator's share accumulates in the contract as a separate line: about 7% of paid bets (10% in rounds settled before program upgrade No. 2). Each withdrawal of it is a public transaction, and the contract does not let him take more than has accumulated.

Whether the code has changed

The program's page in the explorer shows the holder of the upgrade authority and the date of the last deployment. A new deployment is a reason to reread the rules.

Refunded rounds

After a bet is refunded, the project publishes the secret of that round in the refunds folder of the public checker repository. Anyone can check the secret against the fingerprint recorded before the bet. For a round that was sealed before the refund, the report also lets you see what it would have paid; a round refunded unsealed has no recorded block value and therefore no round number.

Odds

The prize tables on the game pages are built automatically from the contract's constants. There are 16 games in total; the expected payout from the tables is the same for all of them.

Read on