Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #4816
−$1.00
whole session · 2 epochs · 1 rounds · 2 steps · $1.00 wagered
final epoch $0.00 · earlier epochs −$1.00
✓ 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
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. Every settled figure below is decoded from the checkpoint transaction's own event — never this site's database.
Proof of randomness · final epoch
✓1.The seed was committed before you played
This epoch's commitment was fixed on-chain by the previous checkpoint transaction (linked in the timeline above), before any of this epoch's steps. 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)
0xfc1d1aeb944f3b112caad4790cac73fe22d9c317dd3be0e0b244e5822e22e5b6
Server seed (revealed at close)
0x2a165f8560daceec961187b48d3af73825e34936a120f89a5bb54a69e834b3e9
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=4816, steps=0, root=0x00000000…00000000)
Recovered signer
0x3055C9200CF44063e84159d4FC02b987E52a4a74 ✓ = your session key
✓3.The stream hash-chain checks out
Round 1 · played against Flip 50% — sealed tree #13game stats →
fold t1 · roll = keccak256(serverSeed ‖ clientSeed ‖ channelId ‖ t) mod 10000
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
0x0000000000000000000000000000000000000000000000000000000000000000
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.
Zero rounds were played — the close is a full refund, co-signed by the player's key (the house cannot refund unilaterally).
✓ The recomputed net, wagered total, and step count match the on-chain close settlement exactly — this proves the final epoch; each earlier epoch is verified against its own checkpoint transaction above.
✓5.Every round respected the committed caps
The channel committed hard walls before play: no stake above the budget of $180.65, and no single round whose worst-case win exceeds the committed per-round cap of $253.42 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.
Games (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)