Fairness

Every GrowBit Original outcome is produced from two inputs: a secret server seed held by GrowBit, and a client seed attributable to players. Before the server seed can affect anything, GrowBit publishes its SHA-256 hash. That published hash is the commitment. Because the outcome is a fixed mathematical function of the two seeds, the same inputs always produce the same result. No clock, no hidden state, and no player-specific adjustment forms part of the calculation.

A commitment establishes that a server seed was not substituted after a bet was placed. On its own it does not establish how that seed was chosen beforehand. If an operator held both seeds at the same time while neither was published, it could search for a server seed that suited the client seed it already knew, and every commitment would still verify. GrowBit addresses this by separating the two inputs in time.

For the games that use a per-player seed chain (Coinflip, Dice, Limbo, Keno, Mines, Towers, Blitz, War, Blackjack and Cases), every generation you create by rotating works like this: GrowBit generates the server seed and publishes its commitment while no client seed exists. You then supply the client seed, generated by default in your own browser. Until you have done so, GrowBit will not issue a bet against that seed generation; the bet is declined rather than assigned a client seed automatically. By the time GrowBit learns your client seed, its own half is already fixed and published. The first generation of each chain is the exception: GrowBit creates it with both seeds at once, so it carries the weaker guarantee until you rotate.

Crash rounds are shared by everyone playing them, so they cannot use a per-player chain. Instead, the round is committed before betting opens, and its outcome is derived only once betting closes, from random values that each participant submits together with their bet. Every contribution is broadcast to all connected clients, so the input used to settle the round can be recomputed independently from the bets that were placed.

While a server seed can still affect an outcome, only its commitment is visible and the seed itself is never disclosed. Crash and Case Battle seeds are revealed automatically when the round or battle concludes. Seed chain seeds are revealed when you retire that generation from Your seeds. Retired generations are preserved permanently, so bets placed on an earlier generation remain verifiable however many times you rotate afterwards.

Each GrowBit Original carries a house edge that is fixed within that game’s outcome logic. It is identical for every player and every session, and no operational interface allows it to be adjusted per game, per player, or per session. The figure is not the same for every game, and the differences are set out below rather than averaged into a single headline number.

Coinflip, Dice, Limbo, Keno, Mines, Towers, Blitz and Crash operate at a theoretical return to player of 96 per cent, equivalent to a 4 per cent house edge. In Mines and Towers the edge is applied once at cash-out rather than at each step, so the theoretical return does not change with how far you progress.

Three families differ. War returns approximately 97.9 per cent on the main bet under optimal play and 97.06 per cent if you always surrender, with each side bet at 94.12 per cent. Blackjack has no fixed edge constant; its return follows from the published table rules and is approximately 99.5 per cent on the main game under basic strategy, with side bets priced separately. Cases are priced within a 93 to 96 per cent band, and the figure applicable to an individual case is shown on that case’s own page.

Published return to player figures are theoretical long-term values. They do not guarantee any particular result over a session or a series of bets.

Bet limits and the maximum single win are held in United States dollars and converted to your play currency at the published configuration rate. These limits are payout controls, not outcome parameters: they can cap what a winning bet pays, but they do not influence which outcome occurs. Every settled bet records the configuration version in force at the time it settled, and every version of that configuration is retained, so a capped payout can be checked against the values that actually applied to it.

Every settled GrowBit Original bet in your history displays the values that produced it. Once the server seed has been revealed, you can independently confirm two things: that its SHA-256 hash matches the commitment published beforehand, and that re-running the game’s published algorithm reproduces exactly the result you were shown.

GrowBit publishes standalone verification tools for this purpose on the Provably Fair implementation page. They have no dependencies and contain no GrowBit code, so running one checks GrowBit’s implementation rather than repeating it. That page also records each algorithm in full, together with the limitations of what verification can establish.

Each seed generation, and each Crash round you join, is accompanied by a commitment receipt: a cryptographic signature over that commitment, which you can save from Your seeds. Anyone can check a receipt against GrowBit’s published key without holding an account. A valid receipt establishes that GrowBit issued that commitment. It does not establish the time of issue, which remains GrowBit’s own assertion, so a receipt is most useful when you save it before you play.

If an outcome still appears incorrect after you have checked it, contact our team with the bet identifier. GrowBit will review the derivation with you.

Slots and other third-party casino games are licensed titles supplied by external providers and delivered through an aggregator. Their outcomes are generated inside each provider’s own random number generator, which may be independently tested and certified under that provider’s compliance framework.

GrowBit does not generate, influence, predict, or reconstruct these outcomes. There is no GrowBit server seed, client seed, or nonce for a third-party game round, and the verification tools described on this page do not apply to them. Their fairness rests on the provider’s own certification.

All GrowBit balances, including Diamond Locks (DLS) and United States dollars, are recorded on a single append-only ledger. DLS is counted in Diamond Locks and shown with two decimals, where 1 Diamond Lock equals 100 World Locks. Every movement of funds, whether a bet, a win, a deposit, a withdrawal, a tip, or a promotional credit, creates a ledger entry, and balances are derived from those entries rather than stored independently. DLS deposits and withdrawals settle through operator-controlled Growtopia bots.

A continuous reconciliation process compares recorded balances against the ledger. Any discrepancy is raised for review and resolved before further movements are permitted on the affected balance.

Verifiable outcomes do not make gambling risk-free, and no fairness mechanism changes the fact that GrowBit Original games are designed to return less than they take over time. Supported balances may hold no monetary value outside their originating games, but the money, items, and time used to obtain them are real. GrowBit provides a self-exclusion control that you may activate yourself and that support cannot reverse on your behalf. Please read the Responsible Gaming guide before you play.