Don't trust the page.
Check the chain.
Everything below is read live from Robinhood Chain by your own browser — not from our server. The draws are recomputed here, line by line.
Reading…
…
Liabilities = live round deposits + rolled-over pot + unclaimed prizes & refunds + team share not yet sent. The contract has no function that lets anyone withdraw player funds.
Seed × block hash → block.
For each settled round your browser checks that the revealed seed matches the hash committed before deposits opened, and that keccak256(seed, block hash, round) mod 25 + 1 gives the paid block. On Robinhood Chain the block hash comes from the chain's sequencer via blockhash(); it is recorded on-chain in the round itself.
| Round | Commit matches seed | Block hash is real | Recomputed block | Paid block | Verdict |
|---|---|---|---|---|---|
| Reading… | |||||
Contract tests.
The contract is tested with Foundry, including a fuzz test that checks balance = liabilities after random deposits and draws. Results from the last build:
Plainly.
- The operator could refuse to reveal a seed. It cannot choose a winner — the outcome also depends on a block hash that didn't exist yet — but it could void a round. Voided rounds refund every deposit in full.
- Block hashes are produced by the Robinhood Chain sequencer. We treat them as unpredictable; a sequencer acting against us is outside what this contract can prevent.
- Rounds are opened by a small keeper bot. If it is offline no new rounds start; existing funds are never stuck — claims and refunds work without it.
- The contract has not had a third-party audit. Read it, run the tests, size your play accordingly.