Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #418
+$1.10
1 round · 2 steps · $0.10 wagered · won
✓ 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)
0x58fcc9f5856d126c3da196c99676a8d4790d2b014b610f3525593b25478acc90
Server seed (revealed at close)
0xcf48ffeeb3a28bad799dfd2377f5e53884c98b801f9c927fae87a7ab4c76f2f0
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=418, steps=2, root=0x7015db62…252abee6)
Recovered signer
0x7CADDe933882b0b6f67b8e3693C8Ce1A24A267ef ✓ = 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
0x7015db627207c14d9a3237c8103f80fea77567763788c438c86c4b80252abee6
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
✓ 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.