Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #1708
−$0.10
1 round · 3 steps · $0.10 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.
Verified in your browser
Re-deriving every check from chain reads in this browser — reconstructing the game trees, re-rolling the seed, recovering the signature…
Don't trust this site's RPC either? Paste any HyperEVM RPC URL and re-run — the verification then never touches this site. The algorithm is verifyChannel in @freeroll/sdk — run it yourself from a terminal for zero trust in this page.
Parameters chain
Proof of randomness
✓1.The seed was committed before you played
The commitment keccak256(serverSeed) was fixed on-chain in the open transaction at block 59418178, before any step was played. The seed revealed at close must hash back to that commitment — since keccak256 has no known way to find a second preimage, the house had exactly one seed it could ever reveal, chosen before it saw a single one of your bets.
Commitment (bound at open)
0x0aea796eb54a1bf53651538e42f5c91240481cd3f7bf7191996c3d3d473ac508
Server seed (revealed at close)
0xbece15ef98c1a44b47e98a86ae6dd5d9f73a7c0c682cf96e23a605bc78b3daa6
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=1708, steps=3, root=0x23f2f3cf…2bc78a10)
Recovered signer
0x023d33e7312415E64fB66411Afd7A8736F4209B5 ✓ = 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
0x23f2f3cf05d4d580998664459f1a8a8c0bb0dc61e7be8fcc223f6c4c2bc78a10
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.
Round 1 · played against game #1 (player-registered set) — sealed tree #1
t1 · you chose option 1 of 6 · worth 0.98× under optimal play · the best option available — no roll here, the choice was yours. Values come from the sealed tree itself.
fold t2 · roll = keccak256(serverSeed ‖ clientSeed ‖ channelId ‖ t) mod 10000
✓ The recomputed net, wagered total, and step count match the on-chain settlement exactly.
✓5.Every round respected the committed caps
The channel committed hard walls before play: no stake above the budget of $10.73, and no single round whose worst-case win exceeds the committed per-round cap of $112.18 against its own game's maximum multiplier. Every round in the stream was re-checked against both — the same integer comparison the contract itself enforces. All rounds fit.
Game (on-chain catalog) chain
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.
What this page proves · what it assumes
Proven (recomputable by anyone)
Assumed (and why it's bounded)