Digger

Bet. From $0.10 to $100 per panel. Two panels are available at the same time — you can bet on both in the same round.

Multiplier and cash-out. The multiplier grows from the start of the round by a known formula, in steps of 0.01 (x1.00, x1.01, x1.02…); the round crashes by itself, and a bet that is not cashed out before the crash is lost. A cash-out pays the bet × the step shown at that moment, that is, the multiplier rounded down to hundredths. The lowest step paid is x1.01: x1.00 is the stake itself, so a cash-out while x1.00 is shown is paid at x1.01 (a round that has not crashed at once always reaches x1.01). The moment the server actually receives your "Cash out" command depends on the network delay — the longer the delay, the later the cash-out is processed (usually at the same or a slightly higher step); the server always uses the step at the moment it receives the command, not at the moment you pressed the button on the screen.

Timing the cash-out is not a skill. The crash point is random and is set when the round starts, before the multiplier begins to grow: choosing the moment changes the probability and size of a win, but not the average return: the higher the target, the less often a round reaches it (a step x from x1.01 is reached in 96% / x of rounds: x2 in 48%, x10 in 9.6%), and for any target the average return is the same — 96%. Experience and reaction speed give no advantage; the network delay can shift the moment the server receives the command (see "Network delay and cash-out"). "Catching the moment" is part of the entertainment, not an advantage.

Keyboard. The Space key does the same as the main button of the first panel (bet, cancel or cash out) when the cursor is not in an input field, the focus is not on another button and no window is open. There are no other hidden controls.

RTP 96%. On average, over a very large number of rounds and bets, the game returns 96% of the amount staked to players. This is a statistical property over the long run, not a guarantee for a single bet or a single session.

Payout cap per bet — $10,000. If the win by the formula would exceed this amount, the bet is cashed out automatically at the highest step whose payout does not exceed it (so the payout can be below the cap by less than 1% of the bet) — this bet cannot grow any further, but the round goes on for the others.

Map cap — x10,000. If the round multiplier reaches x10,000, all bets that are still active are cashed out automatically at x10,000 (or at their own cap of $10,000 if that comes first) — the round cannot go higher than this.

Total payout cap per round — $50,000. If the total payouts to all players in a round approach this amount (the server reserves 1¢ per active bet in advance for rounding, so it triggers a few cents earlier), the remaining active bets are also cashed out automatically at the highest step that fits within it — not by your command, but because the total limit has been reached. This means that in rare cases of a very large round, the bets of other players can affect the moment your bet is cashed out.

Total stake limit per round — $25,000. A bet is not accepted if, together with the bets already accepted in this round (from all players), it would exceed this amount — you can then bet a smaller amount if it fits into what is left, or wait for the next round: bets are accepted again from the next round. This keeps the total payout cap from turning into an instant break-even return when the total activity is extremely high.

Multiplier growth formula. The multiplier grows as m(t) = e^(0.0745·t), where t is the time in seconds since the start of the round, and is shown and paid in steps of 0.01 (m(t) rounded down to hundredths): the same growth rate as in most games of this genre. The crash point is determined by the Provably Fair scheme (see "Fairness" below): from the server seed and the client seeds of the first three bets of the round that carry a player seed. Bet amounts do not affect it. Which players bet first decides whose seeds go into the calculation, but this does not let anyone choose an outcome in their favour: no player knows the server seed before the crash.

Instant crash. A round can end right away at x1.00 — when its crash point is below x1.01; by the game's maths this happens in about 5% of rounds. This is not a failure but a normal part of the fairness formula, built in from the start — as in most similar games.

Payout rounding. The payout — the bet × the step — is rounded to the cent at random: the probability of rounding up equals the fractional part of the exact amount (for example, 13.7¢ becomes 14¢ with a probability of 70% and 13¢ with a probability of 30%). The randomness is cryptographic and does not depend on the moment of the cash-out, so on average the rounding is neutral for any bet amount. The amount on the "Cash out" button is an estimate (marked with "~"): the actual payout is calculated by the server when it receives the command and can differ by ±1¢ and by the growth of the multiplier while the command is on its way.

Multiplier display. The multiplier on the screen is calculated from the server clock, synchronised with your device, so it grows the same way and smoothly for all players. With a poor connection the screen can lag behind the server or briefly show the step after the last one of the round before the crash message arrives; the payout is always decided by the server, by its own time, at the moment it receives the "Cash out" command. The result of a round on the screen and in the history is its crash point rounded down to hundredths (a crash point of x1.999 gives "x1.99"): it is the last step of the round — shown in full, and a cash-out at it still wins; the next step is never reached. The Provably Fair check shows the exact crash point and this result.

Network delay and cash-out. The "Cash out" command takes some time to reach the server — half of the round-trip time of your connection; when the connection is weak, the game warns you. The server calculates the payout at the step of the moment it receives the command — usually the same or a slightly higher step than the one on the screen when you pressed. If the crash happened while the command was on its way, the bet loses, even if your screen has not shown the crash yet. There are no corrections for delay for anyone: the rule is the same for all players. With a weak connection, cash out with a margin or use Auto Cash Out.

Auto bet and auto cash-out. On the Auto tab of a bet panel you can turn on Auto bet, Auto Cash Out or both. Auto bet places a bet of the panel's amount at the start of every round until you turn it off, cancel a bet, go back to the Bet tab, or a bet is refused (for example, when the balance is not enough). Auto Cash Out cashes the bet out at the multiplier you set (from x1.01, two decimals): the server does it at exactly that multiplier as soon as the round reaches it, so the network delay does not matter. If the result of the round (its crash point rounded down to hundredths) is below that multiplier, the bet loses; if it is equal, the round has reached your multiplier and the bet wins. The multiplier is fixed when the bet is placed; you can still cash out by hand earlier. The payout cap per bet, the map cap and the total payout cap apply as to any bet.

Anonymous quality statistics. Allow sending averaged measurements of the connection and smoothness (delay, frame rate, load time) — without balance, bets or identifiers. Off by default.

Cancelling a bet and interrupted rounds. A bet can be cancelled only while bets are being accepted, before the round starts — after the start only a cash-out is possible. If a round is interrupted by a failure or a server restart BEFORE it has ended with a crash, all bets active at that moment are automatically refunded to the players in full, and the round itself is marked void, with no outcome — no money is lost in this case.

If your connection drops. A bet accepted by the server stays in play without a connection. Without Auto Cash Out the server does not cash out a bet by itself — if your "Cash out" command did not reach the server before the crash, the bet loses; with Auto Cash Out the server cashes it out at your multiplier anyway. After you reconnect, the state of the bet and its result are shown on the panel and in "History"; a win, if the cash-out went through, has already been credited.

Casino balance. If the game is opened from a casino and the money is held in your casino account, a bet is accepted only after the casino confirms the debit. If the confirmation does not arrive before the round starts, the bet is not accepted, and any amount already debited is returned automatically. A win is credited to your casino balance right after the cash-out; if the casino is temporarily unavailable, crediting is retried until it succeeds.

Account freeze. If the automatic reconciliation finds a mismatch between the balance and the transaction log, the account is temporarily frozen until a manual check: new bets are unavailable, but bets already placed can be cashed out or (before the round starts) cancelled — a freeze does not take away money a player has already staked.

Actual limit per player per round — up to $20,000. Since two panels are available, each with a payout cap of $10,000, the most one player can get in one round is their sum.

Fairness (Provably Fair). The result of a round is determined by the server seed and the client seeds of the first three bets of the round that carry a player seed: SHA-512 of their concatenation (the server seed, then the client seeds in the order the bets arrived, without separators); the first 13 hexadecimal characters of the hash give a number r from 0 to 1, and the crash point = RTP / (1 − r), but not less than x1.00 and not more than x10,000. The result of the round is the crash point rounded down to hundredths: the round runs through that step and ends when the next one would begin (a crash point below x1.01 ends it at once). If the round has fewer than three bets, the seeds of the bets made are used; if there are no bets — only the server seed. A bet among the first three counts even if it is cancelled later. The client seed is random in every round or your own (menu ☰ → Provably Fair settings). The server seed hash is published before the round starts (the hash of the next seed is in the Provably Fair settings), the seed itself after the crash; the details of any round open when you tap its multiplier in the history strip. Server seeds are fixed in advance in batches of 20, at least 39 rounds before they are used (except the first batches after the server starts); if a round is voided or the server restarts, the seeds are kept sealed with an independent auditor's key and are revealed at an audit.

MODE

ANIMATIONS