Bustabit
review 2026

Bustabit in 2026 — the pedigree pick

If you want to understand why "provably fair" exists at all, Bustabit is where the story starts. The game went live in July 2014 under the name MoneyPot: the launch thread on the Bitcoin Forum is dated 25 July 2014 and was opened by its first operator, Eric Springer. Ryan Havar (known online as RHavar) bought the site in its first year, held its first provably fair seeding event on 12 January 2015 and rebranded it as bustabit. It was one of the very first gambling games to let players cryptographically verify that the operator could not have manipulated an outcome after bets were placed. The crash format that Stake, Roobet, and dozens of others now run as a flagship "Original" traces directly back to this game.

More than a decade later, Bustabit is still live and still almost unchanged: a single multiplier line that climbs from 1.00x and busts at a random point, with players racing to cash out first. There are no slots, no live dealers, no sportsbook, no app — just the crash game and a chat box. That minimalism is the point, and it's also the catch. You're here for one thing, and you should judge it on that one thing.

Honesty first: a long track record is not the same as a clean one. Bustabit has changed hands three times, most recently in February 2024 (more on that below), it holds no gambling licence, and its public reviews are genuinely mixed — strong on fairness, weaker on larger-withdrawal experiences. We rate it as what it is: the best-pedigree provably fair crash game on the internet, wrapped in an unlicensed, no-frills site.

The 1% house edge — what it actually costs

Bustabit's headline number is a 1% house edge, which works out to roughly a 99% RTP. That is genuinely competitive — most crash games and crypto originals land between 1% and 3% edge, and standard slots are far worse. Here is what 1% means for your bankroll versus a typical slot.

How the edge is applied

The edge sits in one constant of the published formula. A round's raw result is 99 / (1 − X), where X is a number between 0 and 1 taken from the round's hash; a game with no edge would divide 100. The result is cut to two decimals, and anything below 1.00x is shown as 1.00x. Ryan Havar, who posted the version 2 formula, put it this way on the Bitcoin Forum on 29 May 2020: the 99 is there "to make a house edge of 1%".

Two things follow, and both are plain arithmetic from that formula rather than anything the operator has to be trusted on. The chance that a round reaches at least a multiplier m is 0.99 / m, against 1 / m in a game with no edge. And about 1.98% of rounds (2 in 101) end at the minimum result of 1.00x — which is why there is no "safe" auto-cashout. Treat the 99% RTP as a long-run average, not a per-session promise.

Arithmetic from the result formula in bustabit's seeding events and verifier source (99 / (1 − X), X uniform between 0 and 1). The bust point is fixed by the same hash chain you can verify.

What changed between version 1 and version 2

The game that ran from January 2015 to January 2018 took its edge differently. Its reference code carries the comment "In 1 of 101 games the game crashes instantly" — those rounds ended at 0x — and it paid a bonus: in the later owner's description, "The bonus was 1% of what was wagered in a round and was paid to the player(s) that cashed out last." Version 2, launched on 27 January 2018, removed both. "Both instant busts at 0.00x and the bonus have been removed and the house edge is now a flat 1 %", the announcement post of 7 February 2018 says, and it is candid about the trade: the edge went up in version 2, but "the majority of players are likely better off in terms of expected value thanks to the removal of the bonus system". Anything written about bustabit's 0x instant crash or last-cash-out bonus describes the pre-2018 game.

Bet and profit limits — a percentage of the bankroll

Bustabit has no fixed table limits. The same announcement post (last edited 11 November 2020) sets the rule: "the most a single player can win in one game is 1% of the bankroll, in line with the Kelly criterion", and "if all players in a game combined would win more than 1.5% of the bankroll, they are also forced to cash out". A player whose win would pass the limit is cashed out at that point rather than refused. On stake size the post says: "The bet limit has been removed entirely, allowing bets of virtually any size."

Because the cap is a percentage it moves with the bankroll. On 5 November 2026, after a run of large player wins, the operator put the maximum profit per game at about 4 BTC. A high roller should read the current figure off the site before sizing a bet around a large multiplier.

The bankroll — who is on the other side of your bet

Since version 2 the money that pays winners is not the operator's own. "bustabit is no longer privately bankrolled. Instead, anyone can invest in the bankroll to participate in the casino's profits (and losses)", the 2018 announcement says. Investors hold shares of one pooled bankroll, players win from it and lose to it, and the operator takes a commission. That is the reason the profit limit above is expressed as a share of the bankroll, and it is also the practical answer to who pays a large win: the pool, not a licence bond or a guarantee fund.

The size of the pool has swung widely, in the operators' own figures. In April 2019: "At over 6,300 BTC, bustabit's bankroll is only rarely fully utilized". In November 2020, with sister site bustadice: "the combined bankrolls still total more than 11,000 BTC". On 1 May 2026: "The bankroll had ~500 BTC and that player alone has already won a little over 82 BTC". After further large wins in early November 2026 the operator wrote that "we've averaged about 3,000 BTC wagered per month over the past year" and that at a 1% edge "it could take around nine months to recover the current 270 BTC deficit" for investors. The current owner said in October 2025 that the commission rate is meant to encourage divestment from a pool he called "still very underutilized (way too big for the current wager volume)".

On custody, the 2018 announcement states that "the majority of funds are held in a multisignature cold wallet by myself, Ryan and a trusted third party". That sentence describes the arrangement under the owner who sold the site in February 2024.

Ownership, licensing & the honest caveats

Bustabit has had four owners. Eric Springer launched it as MoneyPot in July 2014 and put it up for auction that October. Ryan Havar (RHavar) bought it, rebranded it as bustabit and, by his own public account, sold it at the start of 2018 to Daniel (forum account devans), who launched version 2 on 27 January 2018. Daniel in turn sold bustabit and its sister site bustadice to Leo Medina, who took over on 26 February 2024. Today the site is run by Green Train S.R.L., a company registered in Costa Rica, and is governed by Costa Rican law. Those ownership changes matter because the "decade of trust" is split across more than one operator — the brand is continuous, the management is not.

Sources: Bitcoin Forum threads 709185 (launch), 818014 (auction), 2897545 (operator announcements since 2018) and the four seeding threads linked below.

Crucially, Bustabit holds no gambling licence from any recognised regulator. It operates as a crypto-native site that leans on its provably fair model and reputation rather than on regulatory oversight. For the games themselves that is arguably fine — you can verify fairness mathematically. But "unlicensed but provably fair" has a hard limit: provable fairness guarantees the game is honest; it does not guarantee the operator will pay a large withdrawal promptly, and there is no licensing body to escalate to if it doesn't.

The licence position has not been constant, and the operator's own statements show it. When the previous owner introduced terms of service in September 2019 he explained the list of excluded countries by saying bustabit shuts them out "because our gaming license requires it"; in February 2020 he wrote, "I moved the gaming license seal to the bottom of the terms of service"; and in June 2022 he referred to "bustabit's operating company (Apis N.V.)". None of those statements comes from the current owner. Neither Apis N.V. nor Green Train S.R.L. appears in the Curaçao Gaming Authority's Online Gaming License Registry as last updated on 5 November 2026, which lists licences granted under the policy in force since 15 November 2023, and no entry in the Anjouan Gaming licence register (11 November 2026) carries a bustabit domain or either company name. Absence from those two lists shows only that no licence is recorded there under those names; it is consistent with the unlicensed label on this page.

That limit shows up in reviews. Bustabit's Trustpilot page is genuinely mixed. Many long-term players report years of clean deposits and withdrawals. Others report the opposite — withdrawals delayed, large cashouts held, and at least one user describing being stonewalled by support after a dispute. We can't adjudicate individual cases, but the pattern is consistent enough that we score withdrawal reliability well below fairness. Our take: excellent for verifiable small-stakes play; approach large balances with caution and withdraw regularly rather than letting funds sit.

Deposits and withdrawals — Bitcoin in, Bitcoin out

Bustabit runs on Bitcoin alone — "bustabit exclusively uses Bitcoin", as the previous owner put it in February 2021 — and shows balances in bits. One bit is 100 satoshis, or 0.000001 BTC; the operator's script documentation warns that "The client and server talk in satoshis even though the user interface shows bits." What the operator has published about moving money in and out:

The complaints about held withdrawals noted above come from player reviews. The operator statements in the table describe how withdrawals are queued and priced, not how long a large one takes.

The March 2019 hot-wallet incident

The one publicly documented loss of funds at bustabit was a game exploit, not a failure of the fairness scheme. On 21 March 2019 the then owner reported that "an attacker exploited a previously unknown vulnerability in one of bustabit's API methods which allowed him to find out the current game's outcome before its end", winning 122.5686 BTC and emptying the hot wallet. The bug was patched the same day, the hot wallet was refilled, and the loss fell on the bankroll's investors, whom the post undertakes to make whole: "bustabit will reimburse all affected bankroll investors out of pocket". The episode shows where the chain's guarantee stops: the hash chain proves a result was fixed in advance, and for that very reason anyone who can read a result early can bet against the pool.

Accounts, KYC and dormant accounts — what the operator has put in writing

Bustabit does not run identity checks as a routine step for players. The current owner's answer, given on 28 February 2024 a few days after he took over: "We'll request KYC information only in cases where we suspect a player may be underage, from forbidden jurisdictions, or if mandated by law enforcement." His predecessor described the same policy in September 2019 — "a KYC check is only necessary if there is a specific and plausible reason to believe that a user is prohibited from using bustabit" . The terms of service clause behind it, as quoted in the operator's thread that month:

"To ensure that no prohibited users are using the service, the operator may demand proof of age, citizenship and residence of any user at his own discretion. If the user does not provide adequate proof at the operator's request they may be barred from further using the service."

On what happens after a refused or failed check, the 2019 statement is specific: "we may restrict their account from further using the site, i.e. betting, investing and chatting, and demand that they withdraw their funds and refrain from using bustabit going forwards", and, short of a court order, "bustabit will never prevent users from accessing their funds". A player in the United States who asked for clarification that week was told: "since you are from a prohibited jurisdiction I'm afraid I have to ask you to withdraw your funds and stop using bustabit and bustadice." The same reply says "bustabit never has and never will seize users' funds unless it's legally compelled to by a lawful court order". These are the previous owner's commitments; the current owner's statement above repeats the triggers but not the promise about funds.

Bankroll investors are treated differently from players. Since July 2024 new investments need verification of age and of citizenship or residency, and the owner's explanation was short: "we made KYC mandatory based on our lawyers' advice". According to the notice sent to investors, as quoted in the thread, an investor who declines can still divest and withdraw.

Excluded countries

The terms of service introduced in September 2019 listed seven prohibited jurisdictions, as quoted in the operator's forum thread on 20 September 2019: Aruba, Australia, Curaçao, France, the Netherlands, Sint Maarten and the United States of America. That list belonged to the licence arrangement of the time; this review's summary lists the United States, Costa Rica and FATF high-risk jurisdictions as excluded. The operator's stated practice in 2019 was to ask a player from an excluded country to withdraw and stop playing, not to confiscate the balance.

Dormant accounts

This is the clause most likely to cost a long-absent player money. The current owner quoted it on 5 December 2025: "the operator may permanently delete accounts that have not been accessed for two years and may make usernames of deleted accounts available for use with new accounts again". The 2019 text of the terms, as quoted in the same thread, adds the consequence: "All funds of deleted dormant accounts including their balance and any bankroll investments are forfeited by the user and assumed by the operator." Two operator statements narrow it. Access is defined loosely — "Signing in or connecting to the site while already signed in is all that's necessary for an account to be considered active." — and on practice the owner wrote: "In practice, only accounts that haven't been accessed in over five years have been deleted, and only after being notified by email." Anyone holding a balance or a bankroll stake should still sign in at least once every two years.

Data kept, and accounts the operator closes

The 2019 statement on records: "Currently connection logs, deposit histories and withdrawal histories are stored indefinitely." Identity documents collected for a check are used for that purpose only, and the information "is deleted immediately afterwards and is not passed on to any third parties". The operator has also blocked betting on its own initiative; in October 2021 the then owner told a user in the thread, "I disabled betting for your account because I think that you have a gambling problem".

BUSTABIT vs OTHER CRASH GAMES

Who built Bustabit — and why it still matters

The game's first operator was Eric Springer, who opened the launch thread in July 2014 and released the site's code under the AGPLv3. Ryan Havar (RHavar) bought it within months and was, for three years, an unusually transparent operator — active in Bitcoin forums, publishing technical details of the provably fair system, and treating verifiability as a selling point rather than a footnote. His first seeding post credits the design openly: "The original scheme of turning a multiplayer game in which peers do not trust each other was first proposed by Dooglus, refined by Eric and solidified into code by Steve." That ethos is why the crash genre standardised around provable fairness in the first place, and it's the genuine reason Bustabit earns its place in any serious provably fair discussion.

Since Havar's sale in January 2018 the site has had two more owners: Daniel, who ran it for six years and named Apis N.V. as its operating company, and Leo Medina, who has run it since 26 February 2024; the operating company today is Green Train S.R.L. Each handover came with a fresh hash chain and a public seeding event, so the provably fair mechanism remains intact and checkable, which is the part that matters most for the game itself. Both later owners have kept answering players in the public forum thread, and the most recent replies there date from November 2026. But a forum thread is not a regulator, and that — combined with the absence of a licence — is why we treat Bustabit as a respected legacy product rather than a blanket recommendation. The fairness pedigree is exceptional; the operational guarantees are not.

Provably-fair scheme status — the hash chain, the other verifiable model

Bustabit occupies a special place in our verifier support table: it is the reference example of the hash-chain model — the other legitimate provably-fair design, distinct from the per-bet server-seed + client-seed + nonce scheme Stake later popularised. In a hash chain, the entire sequence of game results is generated in advance as a chain of SHA-256 hashes: each revealed game hash provably links to the one before it, so the operator cannot reorder or alter results after the chain is committed.

Two consequences follow. First, our Stake-style verifier deliberately does not claim to reproduce bustabit rounds — different model, different maths; chain verification is done with bustabit's own verifier, whose source is public, or with any SHA-256 and HMAC tool. Second, within its model bustabit’s fairness is among the best-established in all of crypto gambling — the design has been public, studied and independently re-implemented since the first seeding event of January 2015.

The limit is the one this review already states: the chain proves the games are honest; it proves nothing about whether an unlicensed operator pays a large withdrawal promptly. Verifiability and counterparty risk are different axes, and bustabit is strong on exactly one of them.

Four seeding events, four commitments

A hash chain is only as good as its commitment: the operator must publish the end of the chain before the outcomes can be known, and must not be able to pick a chain that happens to suit the house. Bustabit handles both in a public forum post called a seeding event. The post publishes the terminating hash and names a Bitcoin block that has not been mined yet; that block's hash, which nobody can choose, becomes the salt mixed into every result. In the words of the 2018 post: "This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players." Other forum members quote the post so that it cannot be edited quietly. There have been four:

Sources: seeding threads on the Bitcoin Forum (first, second, third, fourth); game ranges and salts as coded in src/constants.ts of bustabit's verifier.

The first post also records what came before it. The event was held "to replace our provably predetermined multipliers" — in 2014 the game only showed a hash of each outcome in advance — and it introduced the outside ingredient: "The client seed will be the block hash of a Bitcoin block that hasn't yet been mined: block 339300." Both changes of owner since then produced a new chain; as the 2024 buyer put it, "as a result of the ownership change, it became necessary to generate a new hash chain".

From game hash to multiplier

The conversion from HMAC output to multiplier has not changed since version 2. It appears in the same form in the 2018, 2024 and 2025 seeding posts and in src/utils/math.ts of the verifier:

1. Take the game's hash, a 32-byte value shown as 64 hex characters on the game's information page.
2. Compute HMAC-SHA256 with the salt as the key (the 64-character block hash, as text; during the Vx period described below, a signature instead) and the game hash, in binary form, as the message.
3. Read the first 13 hex characters of the output as an integer r — in the code's comment, the 52 bits are the "number of most significant bits to use".
4. X = r ÷ 2⁵², a value the code describes as "uniformly distributed in [0; 1)".
5. X = 99 ÷ (1 − X).
6. The result is X rounded down to a whole number, divided by 100, and never less than 1.00.

The chain link is the other half. In the second chain each hash is the SHA-256 of the next game's hash written as a lowercase hex string; in the current chain it is the SHA-256 of the next game's hash as raw bytes — "we have generated a chain of 100,000,000 sha256 hashes by recursively hashing the binary value of the previous hash". The 2018 post gives the test: "To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash." For the current chain, which starts at game #10,000,001, the verifier hashes the game number minus 10,000,000 times. There is no nonce and no per-player seed, and the operator has said why: "In crash each round has one shared outcome for all players, so there's no need for a per-bet nonce (like on bustadice)."

Worked example with published values

Bustabit's script documentation gives a sample hash from the second chain and its result, 3.74. The steps below are arithmetic on that published hash and the published salt; anyone can repeat them with a SHA-256 tool.

The Vx period, February 2024 to October 2025

For about nineteen months a third party sat inside the formula. From the third seeding event the HMAC key was not the salt itself but a BLS signature over the previous game hash and the salt, produced by Vx, a service of ActuallyFair.com; the post explains the choice of signature scheme: "Vx uses BLS signatures so that it is not possible to generate multiple valid signatures for a particular message." When the service announced it would close, bustabit held the fourth seeding event, so that the new salt would again be the hash of a block nobody had seen, and went back to the plain salt on 6 October 2025. The verifier's constants file marks game #12,279,450 as the last Vx game and now carries the Vx signing key, so rounds from that period can still be recomputed without the service.

The owner was direct about what was lost: "Vx used to verify games on behalf of players, contribute to game outcomes, and reassure investors that neither a compromised server nor the house could predict future rolls." What stays, in the same post: "the main guarantee remains: players can still verify every game independently".

What the hash chain does not protect against

• Payment. The chain says nothing about whether a withdrawal is sent. That depends on the operator and the bankroll described above.
• Foreknowledge. Whoever holds the chain's secret knows every future result. The salt stops the house from choosing a favourable chain; it does not stop the house, or an intruder, from knowing the chain. That is mainly a risk to bankroll investors; a leak of a single round's outcome through the site's API is what cost the bankroll 122.5686 BTC in March 2019.
• The round you are in. A game's hash is revealed after the round, so verification is always after the fact. It catches a changed result; it cannot prevent one being attempted.
• Your own check. The guarantee only binds if the terminating hash and salt you compare against are the ones in the dated forum posts and the Bitcoin blockchain, not values shown to you by a look-alike site. The previous owner reported a wave of phishing sites and apps aimed at bustabit players in early 2021.

Frequently asked questions