What BC.Game publishes about Crash
Crash is a shared-round BC Original: one multiplier applies to every bet in the round. BC.Game's help centre calls it "an exciting online multiplayer blockchain guessing game" and gives the price in two sentences: "The RTP is a cool 99%" and "The house edge is 1%, with 99% of each bet going to the bankroll and the remaining 1% reserved for platform operating costs" (How to Play Crash, article dated 27 November 2025, as of 13 Nov 2026). The game's own data on bc.game lists an RTP of 99 for Crash on the same date.
| Item | What BC.Game states | Where |
|---|---|---|
| RTP | "The RTP is a cool 99%"; RTP field 99 | Help centre, How to Play Crash; game data on bc.game (13 Nov 2026) |
| Betting window | "Before the game starts, you have 6 seconds to place your bet" | Help centre (13 Nov 2026) |
| Modes | Classic Crash and Trenball, playable together | Help centre (13 Nov 2026) |
| Trenball payouts | "RED pays x1.96, GREEN pays x2, and YELLOW pays x10" | Help centre (13 Nov 2026) |
| Win limit | "Each player can only win 0.75% of the bankroll per round, and all players can only win 1.125% of the funds per round" | Help centre (13 Nov 2026) |
| Auto cash-out | Sent to the server with the bet, so it executes "regardless of the lag" | Help centre (13 Nov 2026) |
| Chain | 20,000,000 rounds on the chain announced 15 September 2026 | BitcoinTalk notice (13 Nov 2026) |
| Salt | Hash of Bitcoin block 967,100 | BitcoinTalk notice; BC.Game verifier (13 Nov 2026) |
| Formula | floor(99 / (1 − X)) / 100, with X taken from 52 bits of the salted hash | BC.Game verifier and fairness text |
One BC.Game document points the other way. Its help-centre article on house edge says "We recently adjusted the Return to Player (RTP) percentage for our original games, changing it from 99% to 96%", and uses Crash as its example of where to find the figure in the game panel (article dated 26 November 2025). The Crash article is dated a day later and says 99%, the Crash game data says 99, and the verifier's formula has the 1% written into it. On BC.Game's own evidence the 96% notice does not describe Crash.
The formula in BC.Game's verifier
BC.Game links a verifier for each game from its fairness page. The Crash one contains the whole calculation:
hash = HMAC-SHA256(key = salt, message = round hash as bytes)
r = first 13 hex characters of hash (52 bits)
X = r / 2⁵², rounded to 9 significant digits
crash point = max( 1, floor( (100 − h) / (1 − X) ) / 100 ), h = 1
X is a number spread evenly between 0 and 1. A round reaches a target t when 99 / (1 − X) is at least 100t, which happens with probability 0.99 / t. Multiply by the payout t and the return is 0.99 at every target, which is where the 99% comes from. The h in the last line is the house edge in percent; the verifier defaults it to 1.
BC.Game's fairness text works one round by hand. For the hash beginning 6b5124897c3c4, r is 1,887,939,992,208,324 and X is 0.419206889692064; 99 / (1 − X) is 170.4566; rounded down and divided by 100 the round ends at 1.70x. The same text says "All values less than 100 will be set to 100", which is the 1.00x round.
| Cash-out target | Round reaches it | Bet loses | Reached once in | Return |
|---|---|---|---|---|
| 1.01x | 98.02% | 1.98% | 1 in 1 | 99.00% |
| 1.5x | 66.00% | 34.00% | 1 in 1.5 | 99.00% |
| 2x | 49.50% | 50.50% | 1 in 2 | 99.00% |
| 3x | 33.00% | 67.00% | 1 in 3 | 99.00% |
| 5x | 19.80% | 80.20% | 1 in 5.1 | 99.00% |
| 10x | 9.90% | 90.10% | 1 in 10.1 | 99.00% |
| 50x | 1.98% | 98.02% | 1 in 50.5 | 99.00% |
| 100x | 0.990% | 99.010% | 1 in 101 | 99.00% |
| 1000x | 0.099% | 99.901% | 1 in 1,01 | 99.00% |
Arithmetic from the formula in BC.Game's Crash verifier (13 Nov 2026): a round reaches target t with probability 0.99 / t.
The median round ends at 1.98x: half of all rounds finish below it, which is why the verifier colours 1.98 as its midpoint. The formula sets 1 round in 100 to 1.00x outright, and rounding down to two decimals adds every round that would have ended between 1.00x and 1.01x. Together that is X below 1 − 99/101, so 1.98% of rounds, about 1 in 50.5, show 1.00x and pay nobody. BC.Game's fairness text mentions only the first part: "there is a probability of 1% that 100 will appear".
Trenball: three bets on the same round
Trenball lets you bet on the outcome of the round in place of choosing a cash-out. The help article gives the payouts, 1.96x, 2x and 10x, and not the multipliers that separate the colours. With the split those payouts imply, Red winning below 2.00x, Green at 2.00x or above and Yellow at 10.00x or above, the formula prices them as follows.
| Bet | Pays | Wins when the round ends | Chance | Return |
|---|---|---|---|---|
| Red | 1.96x | below 2.00x | 50.50% | 98.98% |
| Green | 2x | at 2.00x or above | 49.50% | 99.00% |
| Yellow | 10x | at 10.00x or above | 9.90% | 99.00% |
Payouts: BC.Game help centre (13 Nov 2026). Thresholds are the ones the payouts imply; chances and returns are arithmetic from the Crash formula.
Red is the only bet here that wins more often than it loses, and it is priced a fraction below the other two. None of the three is a way around the 1%: Green is a 2x auto cash-out under another name, and Yellow is a 10x one.
What limits a win
The Crash game data has no maximum-win figure; the field is empty (13 Nov 2026), where Mines shows 1,000,000x. The limit BC.Game states is tied to the bankroll: one player can win at most 0.75% of it in a round and all players together 1.125%. The help centre does not publish the bankroll's size on that page, so the cap in money is whatever the game panel shows when you bet. The same article says players can buy into the bankroll, in which case they "win when the house wins and lose when the house loses".
Two practical points from the same article. The cash-out button is a message to a server, and "there is a delay between the time you click" and its arrival; an auto cash-out avoids that because it is "sent to the server at the same time when you place your bet". After a disconnection "the platform will try to cash out for you", which BC.Game itself does not present as reliable: it recommends the automatic setting as "the most reliable way".
The chain, its salts and the September 2026 rotation
Every round's hash is the SHA-256 of the hash of the round played after it, so the whole sequence existed before the first bet on it. BC.Game has re-salted or replaced the chain three times, and the verifier lists each change.
| Applies after game | Salt | Announced | Where |
|---|---|---|---|
| #2,561,902 | Hash of Bitcoin block 635,380 | 19 June 2020, "This block has not been mined yet as of this post" | BitcoinTalk topic 5256606 |
| #5,282,960 | Block 758,160 named on 11 October 2022; block 790,100 named on 17 May 2023 for "crash,roulette,baccarat and keno" | Both before the block was mined | BitcoinTalk topics 5416694 and 5453013 |
| #9,614,371 | Hash of Bitcoin block 967,100 | 15 September 2026, with a new chain of 20,000,000 rounds | BitcoinTalk topic 5594155 |
Game numbers: BC.Game Crash verifier (13 Nov 2026). Posts as of 13 Nov 2026.
The September 2026 notice is the one that covers current rounds. It commits to "The hash of round #1 of the new seed chain": c40143afe93b1724d3fdb4e88f4eee73eb419bc18ee1748ba4ea187e1bcb0eed, and names the salt as "The block hash of Bitcoin Mainnet block height #967,100", adding "No substitution will be made." The post is timestamped 02:04 on 15 September 2026, and block 967,100 was mined at 08:37 UTC that day. Its hash, 000000000000000000010283162e089cc99f643ee5043141412e839945afe2f9, is the default salt in BC.Game's verifier.
For games before #9,614,372 the verifier fills in one older salt, 0000000000000000000301e2801a9a9598bfb114e574a91a887f2132f33047e6, which is the hash of block 790,100 named in the May 2023 post. The October 2022 post names block 758,160, whose hash is a different value, so a round from between those two posts may need its salt entered by hand. That matters only for checking rounds from 2022 and early 2023. The help centre's fairness paragraph still describes "a total of 10 million hashes"; the current chain has twenty million.
Verifying a round
- Copy the hash of a finished round from the game's history.
- Open BC.Game's Crash verifier, paste the hash and leave the salt as it is for any game after #9,614,371. It prints the crash point and the points of the rounds before it, each found by hashing the one after.
- Compare the list with the game history. SHA-256 of any round's hash must equal the hash of the round before.
- For the commitment, the chain must lead back to the value in the 15 September 2026 notice. It sits in a public forum post, and a reply posted the same day quotes the notice in full, commitment included, which is the durable part of the scheme.
Our Crash verifier has a BC.Game mode that applies the same formula with the block 967,100 salt filled in and shows the chain link for the hash you paste; for older games, replace the salt with the one above. Crash has no player seed, so the seed fields in the general verifier do not apply to it. Background: what provably fair gambling proves.
BC.Game Crash against the other four
| BC.Game | Stake | Shuffle | Roobet | Gamdom | |
|---|---|---|---|---|---|
| Stated return | 99% | 99% | 99% at every target | None | 99% after a daily allowance |
| Return at 2x from the published formula | 99.00% | 99.00% | Formula not published | 95.52% | 98.00% |
| Rounds set to 1.00x by the formula | 1 in 100 (1.98% show 1.00x after rounding down) | 1 in 100 | Not documented | 1 in 25 | 1 in 100 |
| Salt | Bitcoin block 967,100, named before it was mined | Bitcoin block 584,500 | Bitcoin block 779588 | Ethereum block 26008955 | Bitcoin block 339,300, mined 2015 |
| Commitment | BitcoinTalk, 15 Sep 2026 | BitcoinTalk, 8 Jul 2019 | Post on X, 6 Mar 2023 | Pastebin, 18 Sep 2026 | Fairness page, replaced when a chain changes |
| Stated win limit | 0.75% of the bankroll per player per round | Profit cap per coin | $250,000 per round | Shown in the bet panel | $500,000 profit per bet |
Stake, Shuffle, Roobet and Gamdom: each casino's own documents as of 12 Nov 2026; details on the pages linked below. Returns are arithmetic from each published formula.
What the 1% costs, and what does not change it
At 99% the expected cost is $1 per $100 wagered, whatever the target. The target decides how the cost arrives: at 1.5x two rounds in three win a little; at 100x ninety-nine in a hundred lose the stake. Doubling after a loss, raising after a win or switching targets changes the size and timing of swings and leaves the 99% where it is, because each round's result is fixed by the chain and does not depend on the last one. The Martingale simulator shows how a doubling plan ends.
BC.Game's bonus system prices play by the same edge. Its help centre gives the unlock rate for locked rakeback as "Wagered Amount × House Edge × 1%" (10 Nov 2026). On a game with a 1% edge that is one cent unlocked per $100 wagered, so Crash is a slow way to release a deposit bonus. The auto cash-out calculator gives hit rates for any target; licence, KYC and withdrawal terms are in the BC.Game review.
Sources: BC.Game help centre, How to Play Crash and House Edge/RTP (13 Nov 2026); game data on bc.game (13 Nov 2026); BC.Game Crash verifier (13 Nov 2026); BitcoinTalk topics 5256606, 5416694, 5453013 and 5594155 (13 Nov 2026); Bitcoin blocks 790,100 and 967,100; Deposit Rakeback Explained (10 Nov 2026). Probabilities and returns are our arithmetic from the verifier's formula.