Cloudbet BTC on BNB Smart Chain / BEP20
This page isolates one operator, one asset and one network so the payment evidence cannot be mistaken for a broader multi-network claim.
Deposit direction, withdrawal direction, numeric snapshots, KYC context and wagering records are kept as separate evidence fields.
Exact route scope
The relation shown here is specifically Cloudbet → BTC → BNB Smart Chain / BEP20. Support on another network is not inferred, and an asset-level value is labelled as asset-level rather than presented as network-specific.
This route does not establish jurisdiction access, a no-KYC policy, a fixed payout time, or future cashier availability.
BTC on BNB Smart Chain / BEP20
Values are shown only with their recorded scope and freshness.
| Field | Recorded value | Scope | Source date |
|---|---|---|---|
| Deposit | Verified | Operator route relation | 2026-08-15 |
| Withdrawal | Verified | Operator route relation | 2026-08-15 |
| Withdrawal minimum | 0.00001 BTC | network | 2026-08-15 |
| Withdrawal fee | 0.0000000498 BTC | network | 2026-08-15 |
| Operator fee | 0 BTC | network | 2026-08-15 |
A network fee is a blockchain-cost snapshot, not automatically an operator fee. A missing numeric value remains not verified.
What this route does and does not answer
Established by the record
- The operator and asset are fixed.
- The network label is explicit.
- Deposit and withdrawal directions are evaluated independently.
- Any numeric value retains its asset or network scope.
Still separate questions
- conditional KYC policy context applies at operator level.
- Wagering records are not payment-network support.
- Geo availability and licensing require their own evidence.
- Blockchain settlement can vary after operator processing.
Source records
Direct operator documentation is listed without tracking parameters.
- Cloudbet Crypto Transaction FeesOperator official documentation · checked 2026-08-15