Channel
verifying on-chain…
Channel
verifying on-chain…
v14 · Channel #5912
−$5.48
3 rounds · 7 steps · $13.25 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 65312202, 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)
0x3a75961c48a2c62ddd2ba3246901e687233e3b39443aaf3602aa11830a0be99d
Server seed (revealed at close)
0x2aae349fadd34c1cec20ea38b61ac559431f4479f80a323365df636e3d2743e8
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=5912, steps=7, root=0xedddf79c…3e05a13f)
Recovered signer
0x3055C9200CF44063e84159d4FC02b987E52a4a74 ✓ = 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
0xedddf79c1ad7a80a931e752925daeca175f796e7ca467a73a8f1ac193e05a13f
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 Snowballin' (2,500× top) — sealed tree #209game stats →
fold t1 · roll = keccak256(serverSeed ‖ clientSeed ‖ channelId ‖ t) mod 10000
Round 2 · played against Snowballin' (2,500× top) — sealed tree #209game stats →
fold t3 · roll = keccak256(serverSeed ‖ clientSeed ‖ channelId ‖ t) mod 10000
Round 3 · played against Snowballin' · POWDER DAY+ (2,500× top) — sealed tree #223game stats →
fold t5 · roll = keccak256(serverSeed ‖ clientSeed ‖ channelId ‖ t) mod 10000
fold t6 · 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 $35.22, and no single round whose worst-case win exceeds the committed per-round cap of $313.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.
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)