Casino review
BC.Game
Not enough independent evidence to verify this operator's payout behaviour.
- No public regulatory licence on file.
- Restricted in 11 jurisdictions — verify your location before signing up.
- No Arkham-attributed payout wallet on file, or no observed on-chain payout activity.
- No Level-A own-test withdrawal on record — we cannot independently measure casino approval time.
We have not personally tested withdrawals from BC.Game. This page is an audit profile based on public on-chain activity, license data, and operator-stated information. Approval-time figures are not our own measurements unless the page shows a first-party test record with a published transaction hash.
Operator data below — owner, licence, supported networks, restricted countries — is sourced from the operator's own public pages and verified where possible against regulator registries. We have not yet conducted our own withdrawal test for this operator, so no approval-time or settlement-time measurement applies. Treat any payout-speed claim about this operator as evidence level D (operator-claim) or E (unverified) until we publish a verified test.
Per-network evidence
One row per network we track for this operator. Tier-A entries are first-party measured withdrawals. Tier-B entries are independently observed on-chain settlements from this operator's payout wallet — we did not run the test, but the settlement side is verifiable on the public block explorer. Networks with no evidence are listed for transparency.
No PayoutDB own-test on record for this operator. Network claims and user reports are tracked in the database.
Audit dossier — BC.Game
Deterministic data block generated from our observation records. Each operator page renders a different summary because the underlying evidence differs — no two dossiers are identical.
What we observed
We have not observed any on-chain payouts attributed to BC.Game yet. Our brand promise is on-chain verifiable payout activity, so absence of data is itself a signal — see the verdict rationale below.
Compared with similar operators
Operators with recent on-chain payout activity, regardless of tier.
| Operator | Tier | Payouts 30d | Networks | Latest seen |
|---|---|---|---|---|
| BC.Game this page | C | 0 | 5 | — |
| Roobet | B | 4549 | 7 | 18 Jul 2026 |
| Shuffle | A | 3939 | 7 | 18 Jul 2026 |
| Stake | B | 587 | 7 | 17 Jul 2026 |
Verdict rationale
We classify BC.Game as Tier-C — Watchlist.
- We have neither observed on-chain payout activity from an attributed wallet, nor confirmed the operator's licence on a regulator-hosted registry. Both signals are required for a higher tier.
- We list this operator publicly so readers can see we are tracking it — silence about brands we audit would itself be misleading.
What would change this rating
Upgrade triggers
- An Arkham-verified payout wallet attributed to this operator
- First on-chain payout observed from that wallet
- Licence number confirmed on the regulator's public registry
Downgrade triggers
- Documented payout failure (test or third-party report with evidence)
- Licence claimed but registry check returns no match
Withdrawal background reading
Concepts referenced across this BC.Game audit that PayoutDB explains in depth:
- Approval time vs settlement time — how casino-side review and on-chain confirmation contribute to total withdrawal time.
- KYC triggers at crypto casinos — when document verification applies and what gets requested.
- Evidence grading (A through E) — what PayoutDB's level-A own-tests prove and what other levels do not.
- USDT TRC20 vs ERC20 — network choice for BC.Game payouts and trade-offs in fee and settlement window.
- First-party tests vs observed evidence — the difference between PayoutDB's measured withdrawals and on-chain settlement observation.
- Withdrawal verification methodology — how the tests on this page were conducted.
- Casino withdrawal with no transaction hash — diagnostic when BC.Game or another operator shows no hash on a completed withdrawal.
- ERC20 confirmed but not received — diagnostic when an on-chain confirmation exists but the receiving wallet shows no balance change.