BC.Game Review: 10 USDT In, 186 Rounds of Crash, 20 USDT Out

Hunting for a Crash bonus that didn't exist

09:26 UTC. The plan was simple: make an account, deposit some ETH, start playing. Then a deposit bonus banner on the homepage caught my eye, and I spent most of the day on the promotions page instead.

I was looking for anything that applied to Crash or Plinko. There was nothing. Every promotion I opened was tied to games from third-party studios: slots, live casino, table games. None of BC.Game's own provably fair games, Crash, Plinko, Mines and the rest, had a single offer attached.

The headline numbers also shrink when you look closer. Before I signed up, games advertised a "220% Deposit Bonus". After I signed up, the same prompt said "+180%". The bonus calculator explained the gap: the first of four monthly deposit bonuses is 180% plus 40% rakeback, and the calculator adds the two into one "Bonus Match: 220%". The overview also says the four-stage offer is exclusive to new users and available for 24 hours only, which isn't what "Monthly Deposit Bonus" suggests.

The prize pools work the same way. "€10K PRIZE POOL" is the big line. "Win up to €1000" is the small one underneath.

On a 10 USDT deposit, any of these bonuses would have been worth cents. I left them alone and went looking for Crash. When I come back to take one, what it took to clear it goes on my Wagering Tracker.

Asking support how the bonuses work

The live chat answers in under a second, from an agent with a name and a smiling photo. I got Nova, Aiden and Davidson across my chats. The first replies are fast and generic. After a couple of canned answers, a question it calls complex gets passed to another agent, and the replies slow down to a normal pace.

So I asked one agent directly: "are you a bot or real person?" The answer was "Haha, fair question", followed by an offer to help. Not a yes, not a no. A real person may sit behind the chat, but a player asking a plain question deserves a plain answer.

I didn't put my three money questions to support during this session, so the support check isn't graded yet.

Signing up, and the wallet I didn't connect

The sign-up window offers more doors than you'd expect: email, Google, Cwallet, and behind "More" a row of others including X, Telegram and MetaMask. If you're new to crypto, it isn't obvious which one is safest.

I tried MetaMask first. It wasn't really a sign-up, it was a request to connect my wallet to BC.Game. I want to decide how much money goes in, so I backed out and signed up with a plain email and password.

BC.Game didn't ask for my name, my phone number or anything else. That's a real difference from the last two casinos I tested: Roobet wanted my name, date of birth and address before my first deposit, and Stake checked my ID before my first bet. It gave the account a random username, and my email doesn't appear anywhere on the account screens. Login and withdrawals are protected by a code sent to that email. No authenticator app, no phone.

Sending 10 USDT

BC.Game handles wallet deposits through Mesh, a third-party service that connects wallets and exchanges. Again it offered to connect MetaMask. Again I declined and chose pay by address.

I had planned to send ETH. The flow would have converted it to USDT on arrival, so an "ETH deposit" isn't held as ETH. That's a conversion on top of Ethereum gas, worth knowing if you deposit large amounts. I had USDT in the same wallet, so I sent that instead, on ERC20.

10:51:23 UTC, sent. 10:51:56 UTC, credited. Thirty-three seconds, and about $0.31 of ETH in gas. Faster than I expected on Ethereum mainnet.

186 rounds of Crash

12:48 UTC. My first bet came almost two hours after the deposit. I spent that time on the settings: auto bet, strategies, Trenball against Classic. I chose Classic and cashed out by hand. Crash has keyboard shortcuts under the settings icon at the bottom left. I checked they work, then forgot about them once I started playing.

I planned an hour. I played for 3 hours 46 minutes. The last bet went in at 16:33 UTC. BC.Game's own statistics panel has the totals:

• Rounds played: 186
• Cashed out before the crash: 109, or 58.6%
• Crashed before I cashed out: 77, or 41.4%
• Smallest bet 0.10 USDT, largest 6.20 USDT, average about 1.43 USDT
• Total staked: 265.27 USDT, 26 times my deposit
• Total paid back on cash-outs: 316.07 USDT
• Balance when I stopped: 60.79 USDT, up 50.79 on my 10

The bet sizes tell their own story. 30 rounds under 0.50 USDT, while I was feeling it out. 40 between 0.50 and 1. 34 between 1 and 2. Then 78 between 2 and 5, where I spent most of the session, and 4 above 5. My appetite for risk grew with the balance, and I didn't notice until I read the log.

The log also corrected my memory. I'd have told you I played two hours straight without writing a note. In fact there's a 109-minute gap with no bets, from 13:22 to 15:11 UTC, when I was writing and reading promotions. Then 140 rounds in 83 minutes, one every 30 to 35 seconds. That was the stretch where I stopped taking notes and the game took over.

The last hour, two losing streaks and a 22x

By the final hour I'd convinced myself I understood the game. I had winnings to spare and decided to chase big multipliers at 2 USDT a round.

16:05 to 16:08 UTC: seven losses in a row at 2 to 4 USDT. Down 26 USDT in three minutes.

16:17 to 16:23 UTC: fourteen losses in a row at 2 USDT each. My balance went from the low thirties to about two dollars in six minutes. I nearly stopped there to withdraw what was left.

16:30:46 UTC: one more 2 USDT round. I cashed out at 22.37x for a 44.74 USDT payout. A few rounds later I was at 60.79 USDT, and that was the moment it registered: I'd come with 10. I stopped.

Two smaller things happened over the session. One round, the interface flickered and didn't respond the way the previous ones had. On another, I felt a lag between my click and the cash-out that may have cost me about 2 USDT. I can't tell whether that was my reflexes, my connection, BC.Game's servers or the interface. The other rounds felt instant. In a game decided by timing, even one lag matters.

I'm writing this part down plainly because it's the most useful thing in the review. Every bet was my choice. Looking back, the bets went up every ten rounds or so, and the last hour was emotional, not calculated. This is how a small, casual session turns into something else. I came out ahead. Plenty of sessions like this end at zero.

Getting paid, with nothing but an email code

I had 60.79 USDT and withdrew 20.25. I left the other 40.54 USDT on the account on purpose, to test Plinko, Mines and Dice next. That balance is still exposed to the casino until I take it out.

The cashier showed different terms at different moments. An earlier attempt, on Tron (TRC20), showed a 1.00 USDT fee and a 21 USDT minimum. The screen I used for the actual withdrawal showed a 0.25 USDT fee and a 20.25 USDT minimum. The withdrawal went out on Ethereum, so that second screen was ERC20. Ethereum coming out cheaper than Tron is the opposite of what I expected, and the screens don't say why.

Before it would send, BC.Game asked me to verify my account with one method. I chose email, typed in the code, and confirmed, the same single step FortuneJack asked for on my withdrawal there. No documents. No name. No phone number. Not even at a moment when plenty of casinos would ask.

18:55:16 UTC, withdrawal confirmed. BC.Game reported 20 USDT on its way, marked "Broadcasting", and 20 USDT arrived in my wallet: the 20.25 I asked for, minus the 0.25 fee. The transfer is in Ethereum block 26,293,161, timestamped 18:55:35 UTC. Nineteen seconds from my confirm to coins on-chain, and BC.Game paid the gas.

BC.Game does have a KYC section in the account settings. I never touched it. It promises "uncapped power and priority payouts" for completing it, without saying what the cap is, and warns that "Verification attempts are limited." If you plan to play big, I'd do the verification before you need a large withdrawal, so a blurry photo doesn't cost you a retry at the worst moment. At 20 USDT it simply didn't come up.

No hold. No documents. One email code, which is how BC.Game confirms every withdrawal, and a fee it showed me before I pressed the button. Paid in full well inside 24 hours: by my rules, the cash-out is a Pass.

The bonuses that followed, in tokens I didn't know

I took no welcome bonus, but small rewards arrived anyway. On deposit day, 6.977723 BC was paid as "Instant $BC" and moved straight into "BC Engine Stake", BC.Game's own staking product, and 0.026526 BCD came as deposit rakeback. Then a Daily Bonus of 0.106223 BCD on October 29 and a Weekly Bonus of 0.21222 BCD on October 30. The rewards panel valued my claimable total at $0.10. All in, about 49 cents.

The weekly bonus came with a twist: claim it, or play "Double or Nothing", a scratch card to win twice the bonus or lose it. A gamble attached to a reward for gambling.

Then the tokens. In crypto, BCD is the ticker of Bitcoin Diamond, a fork of Bitcoin. At BC.Game, BCD means BC Dollar, the casino's own token, and BC is another of its tokens. BC.Game runs its own swap to convert between them and other coins. I nearly swapped ETH into "BCD" on my first deposit attempt, assuming it was a coin I knew. Every reward I received paid in BC or BCD, not in the USDT I deposited.

The money is small. The frequency is not. Quests, doors to unlock, a Halloween frame, notifications for each. "Rookie Quest: First Blood!" landed after my first Crash bet, and the next task was to spin 20 slot rounds. It's built to bring you back every day, and to pull you towards slots while it does.

One more thing about the catalog. The BC Originals tab, where you'd expect BC.Game's own games, also lists third-party slots like Ander Meegan and Ganesha by Croco Gaming. The games I can call provably fair from what I saw are the simple in-house ones: Crash, Fast Crash, Dice, Hash Dice, Mines, Plinko, Keno, Limbo, Twist, Wheel and Double. For everything else, "crypto" describes how you pay, not how the result is made.

Checking my best round against BC.Game's formula

I checked the 22.37x round: bet ID 1880311774358268555, game 9,742,375, 2 USDT staked, 44.74 USDT paid.

First, finding the verifier. It isn't in account settings or the top menu. Open the Crash page, scroll past the game to your bet list, click a round to open its game-detail page, then press Verify beside the hash. Four clicks, no explanation on the way.

Crash doesn't work like Dice. There's no client seed and no nonce. BC.Game generates one long chain of SHA-256 hashes in advance, and each round uses the next hash in the chain, combined with a public salt. The salt for the current chain is the hash of Bitcoin block 967,100. BC.Game announced that choice on Bitcointalk before the block was mined, so it couldn't pick a salt that suited it. I looked the block up on a public explorer myself, and its hash matches the salt the verifier uses, character for character.

BC.Game's verifier gave the round a bust of 30.95x. So it crashed at 30.95, I cashed out at 22.37, and my payout was genuine.

Then I recalculated it outside BC.Game. My first attempt used the classic Bustabit Crash formula and got 30.96x, one cent off. That cent was my mistake, not BC.Game's. The verifier's own code uses a different formula: take the first 52 bits of HMAC-SHA256(salt, game hash), turn them into a number X between 0 and 1, and the result is 99 ÷ (1 − X), floored to two decimals. With that formula my script produces 30.95x, matching the verifier and the game. The 99 is the house edge in plain sight: a 1% cut on every round.

That's half the check. The other half is proving this round's hash belongs to the chain BC.Game committed to in public. Its notice gives the commitment as the hash of round 1 of the new chain. Hashing my round's hash forward should reach it. I ran three million SHA-256 steps both as text and as raw bytes, and never hit it. Either I have the numbering wrong or I'm missing a step. Until it links, provably fair stays open by my rules. It's the mirror image of my Roobet Dice check, where the seed matched its commitment but I couldn't recalculate the roll. (It linked the next day. Here's how.)

What provable fairness does and doesn't prove is worth one paragraph. It proves BC.Game ran the published formula on a result fixed in advance. It doesn't make the formula generous: that 1% edge is how the house wins over thousands of rounds. It says nothing about how the game feels, the animation or the timing. And it only covers the in-house games; the slots and live tables run on their studios' own systems.

The chain links, 9,742,374 steps later

I went back to the verifier's own code instead of guessing. It builds the chain by hashing each game hash as plain text, the 64 characters you see, not as raw bytes. I'd tried that the day before. What I hadn't done was go far enough.

From my round's hash, BC.Game's published commitment came up after exactly 9,742,374 SHA-256 steps. That's one fewer than the game number, 9,742,375. So "round 1" in the notice is game 1, and my round sits 9,742,374 hashes further along the same chain. On a laptop it took about four seconds.

Why that settles it: BC.Game published the commitment on Bitcointalk in September, before the Bitcoin block that supplies the salt was mined, and seven weeks before I played. Nobody can run SHA-256 backwards, so BC.Game couldn't have swapped my round's hash for a friendlier one without breaking the link to a number it had already made public. The result was fixed before I bet, and the published formula turns it into exactly the 30.95x I saw. By my rules, provably fair is a Pass.

One thing doesn't add up, and I'd rather say so. The notice describes a new chain of 20 million rounds, and the verifier says the switch came after game 9,614,371. My round is only about 128,000 games past that. Yet it's 9.74 million hashes from the commitment, which fits one long chain counted from BC.Game's first Crash game, not a fresh one. It doesn't weaken the check, because the commitment still pins my round. It does mean the notice's description and the chain don't match, and it's on my list of questions for support.

The license, on Anjouan's own register

BC.Game's homepage says it's operated by Twocent Technology Limited and licensed by the Government of the Autonomous Island of Anjouan, Union of Comoros, under licence ALSI-202410011-FI1. A badge proves nothing, so I searched the Anjouan Gaming Authority's public register myself.

One row, out of 1,287 licences: Twocent Technology Limited, status Valid, licence ALSI-202410011-FI1, issued October 2, 2024, expiring October 1, 2027. Twelve domains are listed under it, bc.game among them, alongside hash.game, bc.fun and bc.poker. The holder on the register matches the company on the site.

Who's behind Twocent is harder. It's a Belize company, number 41939, at an address in San Pedro on Ambergris Caye. That comes from Sweden's gambling regulator, which in June 2026 banned Twocent from offering games in Sweden without a Swedish licence. Nothing I found names an owner or a director.

The history explains some of the fog. BC.Game used to run from Curaçao, first through Blockdance B.V., then Small House B.V. In November 2024 a Curaçao court declared both bankrupt over unpaid player claims, and in December BC.Game gave up its Curaçao licence and moved to Anjouan under Twocent. Anjouan's own standing is disputed by the Comoros government, which I covered on my crypto gambling statistics page.

So the licence is real, current and in the right name, but I can't tell you who owns the company holding it. By my rules, that's a Caution: on the register, with ownership I can't pin down. More on who's behind BC.Game.

The money so far

The bonuses, about 49 cents in BC and BCD, aren't in this table. The 50.79 USDT is a gambling result, not money in my wallet: so far I've taken out 20, and the other 40.54 is still at BC.Game. The game results come from BC.Game's statistics panel and my own bet log.