Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #305
−$0.09
2 rounds · 9 steps · $0.20 wagered · lost
✓ Provably fair — the seed was committed on-chain before play, the exact step stream was signed by the player's key, and every roll, decision, and payout below is re-derived from public inputs and matches the on-chain settlement.
Parameters
Proof of randomness
✓1.The seed was committed before you played
Before this channel opened, the house bound keccak256(serverSeed) on-chain. The seed revealed at close must hash back to that commitment — the house had exactly one seed it could ever reveal, fixed before your first step.
Commitment (bound at open)
0xb224be9b55c27a0b2b3eaca0358dfe7fbdec49233952a23e659122366b0a651a
Server seed (revealed at close)
0xb590b5fa3a6c194b2e277e8f22399487adfd54fa45c5d1e4ae65e1e36bb41916
keccak256(serverSeed)
✓ matches the commitment
✓2.You signed the exact stream that settled
Each step, your session key signed DrawCommit(channelId, steps, root) — a running hash-chain over every round you entered, every decision you took, and every reveal you requested, signed before the outcome was shown. The close can only settle a stream and count carrying your signature: the house can't add, drop, or reorder a single step.
Signed message
DrawCommit(channelId=305, steps=9, root=0x4ec3be83…f7cd930f)
Recovered signer
0x00c5A5AE99000D8879e3942578ac8aa49dFaDa27 ✓ = your session key
✓3.The stream hash-chain checks out
Re-folding the submitted stream — root_t = keccak256(root_(t−1), t, …) over each round's (stake, game), each decision's choice, and each reveal — must reproduce the root you signed, pinning the exact sequence to your signature.
Signed root
0x4ec3be83cf1fd4e7896e42672e4bad2080292a0fcd331f3a0efd407df7cd930f
Recomputed from the submitted stream
✓ identical
✓4.Every roll re-derived from public inputs
Each roll is keccak256(serverSeed, clientSeed, channelId, t) mod 10000, walked through the on-chain game tree it was played against. Recomputed below — not read from anywhere.
Played against Heist — sealed tree #66game stats →
t1 · player chose option 3 of 3 — no roll, the choice was yours
fold t2 · roll = keccak(seed, clientSeed, id, 2) mod 10000
Played against Heist — sealed tree #66game stats →
t4 · player chose option 1 of 3 — no roll, the choice was yours
fold t5 · roll = keccak(seed, clientSeed, id, 5) mod 10000
t6 · player chose option 1 of 3 — no roll, the choice was yours
fold t7 · roll = keccak(seed, clientSeed, id, 7) mod 10000
t8 · player chose option 4 of 4 — no roll, the choice was yours
✓ The recomputed net, wagered total, and step count match the on-chain settlement exactly.
Game (on-chain catalog)
Each game is a value tree stored on-chain and validated by the contract when it was sealed — the edge under optimal play is enforced inside a fixed band, so no game referenced here can be unfair in either direction. The payouts above were walked from these exact trees, reconstructed from the chain's packed words.