Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #306
−$0.24
6 rounds · 12 steps · $0.60 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)
0x5642c6510bcf4bf27050732be489da6d107b1a7180c8d9d9652308d2829a6e7f
Server seed (revealed at close)
0xcc50994d0fcb588ac3c7019fe79fb499e7f3e4ec74987e1ee121885c2f1510eb
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=306, steps=12, root=0x64d056b8…f44b3d74)
Recovered signer
0xaA7A1E9a871148C4849D4779F2feAd0c8C49fb50 ✓ = 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
0x64d056b87d46d2a11e91f08e281e0f879601132c8c7b974e4dfc7787f44b3d74
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 Cascade — sealed tree #67game stats →
fold t1 · roll = keccak(seed, clientSeed, id, 1) mod 10000
Played against Cascade — sealed tree #67game stats →
fold t3 · roll = keccak(seed, clientSeed, id, 3) mod 10000
Played against Cascade — sealed tree #67game stats →
fold t5 · roll = keccak(seed, clientSeed, id, 5) mod 10000
Played against Cascade — sealed tree #67game stats →
fold t7 · roll = keccak(seed, clientSeed, id, 7) mod 10000
Played against Cascade Surge — sealed tree #68game stats →
fold t9 · roll = keccak(seed, clientSeed, id, 9) mod 10000
Played against Cascade Surge — sealed tree #68game stats →
fold t11 · roll = keccak(seed, clientSeed, id, 11) mod 10000
✓ The recomputed net, wagered total, and step count match the on-chain settlement exactly.
Games (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.