Coin flip
A small, separate side game: bet on heads or tails at even money. It is not a launchpad feature and shares nothing with launching a token - it lives at /flip on its own. What it does share with the rest of Degenland is a refusal to overclaim: this is a house commit-reveal game that is provably fair, and it is careful to tell you exactly what that does and does not guarantee.
What it is
You stake the chain’s native coin on a side of a coin. Win and you roughly double it; lose and the stake stays with the house. There is no token, no curve, no leverage - it is a coin flip. The interesting part is how the result is decided, because the honest answer is more careful than “random.”
- Game
- Even-money flip
- Fairness
- Commit-reveal
- Default edge
- 2%
- Payout
- ×1.96
Robinhood Chain has no verifiable randomness beacon (no VRF, no entropy oracle), and its on-chain entropy sources are predictable or proposer-controlled. So the game does not pretend to be trustless. Instead it is house-provably-fair: the house commits to a secret before you bet and publishes it afterwards, so every past result can be recomputed and checked by anyone. That verification path is the product.
Provably fair, precisely
The result of your flip comes from four inputs, hashed together:
- a server seed the house commits to (publishes only its hash) before any bet binds to it;
- a client seed you supply - the one input the house cannot choose;
- your address and your own per-player nonce (your personal bet counter, not a global one).
After the round closes, the house publishes the server seed. Anyone can then re-hash the four inputs and reproduce your result - the app exposes exactly this check. Because of how the commit and reveal are ordered, several things the house cannot do:
| The house cannot… | Because |
|---|---|
| Change a result after seeing your bet | The seed’s hash is on-chain first; the reveal only accepts a preimage of that exact hash. |
| Grind your outcome by reordering transactions | The nonce is per-player, so nobody else’s transaction - the house’s included - can move you onto a different outcome. |
| Profit by going quiet and never revealing | A bet whose round is not revealed by its deadline settles as a WIN. Silence is strictly more expensive than honesty. |
| Front-run its own reveal | A round stops taking bets at least one block before its seed may be published. |
The one thing you must do
The house can still choose the server seed - that is fine, as long as it cannot also choose your client seed. If you accept a client seed the operator’s own front end generated for you, the house knows both halves in advance and the entire fairness argument collapses. A player who does not supply their own client seed is trusting the operator completely. Type your own - the interface lets you.
The odds
The game is even money less a fixed house edge. A winning bet returns 2 × wager × (1 − edge); at the default 2% edge that is a ×1.96 payout, and your expected value is exactly −2% per unit staked on a fair coin. The edge is the real, disclosed take - not a hidden haircut - and it is capped in the contract at 10%, so it can never be turned into a confiscation after players have learned the odds.
Bet size is bounded
The house caps how much any single bet can put at risk relative to its free bankroll (default 1%), so one lucky wager cannot drain it and the house’s variance stays a business problem, not a solvency one. The app shows the maximum it will accept right now.
Your money is never trapped
The contract holds a solvency invariant at all times: its balance always covers the full payout of every open bet plus every settled-but-unwithdrawn win. Consequences that matter to you:
- Settlement is permissionless. Anyone can settle any bet - it only moves numbers, never sends coin - so a win cannot be stuck behind an unresponsive operator.
- Payouts are pull-based. A win credits your balance; you withdraw it yourself whenever you like.
- The owner cannot reach staked funds. Admins can only ever withdraw the free bankroll - the balance left after every obligation. There is no code path that reaches money that is at stake or owed to a player.
Is it live?
Dormant - the game is built but stays dormant until its contract address is configured on a deployment, like the other dormant features on the status page. It also deploys deliberately closed on several independent axes (paused, an empty jurisdiction allowlist, KYC attestation required), so opening it is always an explicit set of decisions.
Even where the game is configured, a coin-flip wager runs two compliance gates on every bet: a jurisdiction control (allow- or deny-list) and a KYC / attestation check that fails closed if the provider is unset or misbehaves. Wagering products may simply be unavailable depending on where you are. When it is off on a deployment, the page says so plainly rather than pretending. Find it at /flip.