Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #5185
+$0.72
1 round · 2 steps · $0.72 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.
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 62998595, 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)
0x0829d12af57ebdea327e8636da501d84fdf95d7a0f4a7ea3483a376d0361b8f8
Server seed (revealed at close)
0x1cc6fb05f9bba8c83348389101f0afcc4251dda4ba2b3c31ebdd7aa90bad6dbc
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=5185, steps=2, root=0x0992b91b…66c1018d)
Recovered signer
0x3B84E4f30bc398d14aa6A4BCC51a2B504237494c ✓ = 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
0x0992b91b2284acb850b530a7b08343b8a58aa74d8407b11da7621c6266c1018d
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 Streak 256× — sealed tree #75game stats →
fold t1 · roll = keccak256(serverSeed ‖ clientSeed ‖ channelId ‖ t) mod 10000
⏏ The final round ended mid-play, so it settled at the position's table value — the same mark the contract paid.
✓ 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.11, and no single round whose worst-case win exceeds the committed per-round cap of $277.25 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)