Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #378
+$11.47
whole session · 2 epochs · 7 rounds · 14 steps · $8.08 wagered
final epoch +$3.10 · earlier epochs +$8.37
✓ 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
Session epochs
This channel re-armed itself mid-session 1 time: each checkpoint settled the epoch's net, revealed its seed, and committed a fresh one — one continuous session, several sealed proofs. Every epoch below is replayed from its checkpoint transaction's signed stream — rolls re-derived, nets recomputed, signatures recovered ✓ and the chain of commitments anchors to the on-chain channel state.
Played against Cascade — sealed tree #67
Proof of randomness · final epoch
✓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)
0x460ca47ae0fd91a4c76c1972bc3eaebe660acb4d9a4f0f5b4d32c54772770b52
Server seed (revealed at close)
0xeaa161ba8cbe26eac1d3e9b3fe713ff07a2bc0515047ea603dd10e69a12be588
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=378, steps=12, root=0x33e22a4a…467aaf5c)
Recovered signer
0xE434e52c24f6CDa230674b146e381d444B54B6A4 ✓ = 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.
fold t1 · roll = keccak(seed, clientSeed, id, 1) mod 10000
Signed root
0x33e22a4a9ebb9c2ac7a141dc5171450e91a4c54b436b1eccd9e750fa467aaf5c
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 — sealed tree #67game stats →
fold t9 · roll = keccak(seed, clientSeed, id, 9) mod 10000
Played against Cascade — sealed tree #67game 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.
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.