Stake dice odds and house edge, worked out
You can run any strategy you like on Stake dice, but you're running it inside one fixed equation. Knowing that equation tells you exactly what a strategy can and can't do — and how to size bets so a normal losing streak doesn't end the session.
The payout formula
Stake dice rolls a number from 0.00 to 99.99. You choose a win chance p (as a percentage) and whether to roll under or over. The multiplier is:
multiplier = 99 / p
| Win chance | Multiplier | Fair multiplier | Edge |
|---|---|---|---|
| 95% | 1.0421× | 1.0526× | 1% |
| 75% | 1.32× | 1.3333× | 1% |
| 49.5% | 2.00× | 2.0202× | 1% |
| 10% | 9.9× | 10× | 1% |
| 1% | 99× | 100× | 1% |
The fair multiplier would be 100 / p. Stake pays 99 / p. The difference is exactly 1% at every chance — the house edge is the same whether you bet at 95% or 1%. What changes is the variance: low chance means rare, large wins; high chance means frequent, tiny wins.
What 1% costs per hour
Expected loss = 1% × total wagered. The strategy doesn't matter for this line; only turnover does.
| Average bet | Bets / second | Wagered / hour | Expected loss / hour |
|---|---|---|---|
| $0.10 | 3 | $1,080 | $10.80 |
| $1.00 | 3 | $10,800 | $108 |
| $1.00 | 6 | $21,600 | $216 |
This is why bots feel like they "leak" even when the strategy seems fine — a bot's only superpower is turnover, and turnover is what the edge is charged on. It's also why rakeback matters more to a bot user than to anyone else: it refunds a slice of exactly this number.
Streak probabilities
The probability of losing n times in a row is (1 − p)^n. Two things people get wrong: streaks are far more common than intuition says, and a bot rolls enough times per hour to find them.
| Win chance | P(10 losses) | P(20 losses) | Losses for a 1-in-10,000 streak |
|---|---|---|---|
| 95% | 1 in 10¹³ | — | 3 |
| 75% | 1 in 1,048,576 | — | 7 |
| 49.5% | 1 in 1,076 | 1 in 1.16M | 14 |
| 25% | 1 in 18 | 1 in 316 | 32 |
| 10% | 1 in 2.9 | 1 in 8.2 | 87 |
| 1% | ≈ always | ≈ always | 916 |
Read the last column as "the streak you must be able to survive for a session of ~10,000 cycles". A 49.5% martingale needs to fund 14 doublings — 16,384× base — to survive a 1-in-10,000 event. At 1% chance a recovery strategy needs to fund ~916 consecutive losses. Whichever family you run, size the base bet from that column, not from the average.
"Due" numbers and hot seeds
Each roll on Stake dice is generated from a server seed, your client seed and a nonce, hashed with HMAC-SHA256. The result of roll 1,000 is not influenced by rolls 1–999. A number is never "due", a seed is never "hot", and a streak of 20 losses does not make a win more likely on roll 21 — the probability is still p. Rotating your client seed changes the sequence you get, not its distribution; it's fine as a ritual, but it has no effect on expectation. (Details in how Stake dice is provably fair.)
What strategies actually control
- Shape of the profit curve — steady grind with rare cliffs (martingale, recovery) vs. noisy drift (flat) vs. bursts (Paroli).
- Bust probability per session — determined by peak bet vs. balance.
- Turnover per hour — and therefore expected loss and rakeback earned.
They do not control the sign of the expectation. That's fixed at −1% of turnover. Once you internalise that, strategy choice becomes what it should be: picking the session shape you enjoy and capping the downside with stop-loss and vault. See the strategy families for which shape is which.
Keep reading
- Stake Dice Strategies Explained: Martingale, Recovery, Flat-Reset and Which to Actually Run
- How to Run a Dice Bot on Stake in 2026 (Side-Panel Extension, No Scripts to Paste)
- Martingale on Stake Dice: Why It Always Busts, and How Recovery Strategies Differ
- Stake Mirror Sites 2026: stake.jp, stake.bet, stake1xxx.com — Full List and Does DiceStrats Work on Them
- Stake VIP Levels & Rakeback Explained: Bronze to Obsidian, and How Dice Bots Climb Them