Crypto Casino Hub
Cloudbet · ETH over Arbitrum

Cloudbet ETH on Arbitrum

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.

Operator profileETH overviewNetwork researchWithdrawal evidence

Exact route scope

The relation shown here is specifically Cloudbet → ETH → Arbitrum. 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.

Verifieddeposit direction
Verifiedwithdrawal direction
1source records
0wagering records in operator context
Payment facts

ETH on Arbitrum

Values are shown only with their recorded scope and freshness.

Cloudbet ETH Arbitrum route evidence.
FieldRecorded valueScopeSource date
DepositVerifiedOperator route relation2026-08-15
WithdrawalVerifiedOperator route relation2026-08-15
Withdrawal minimum0.0002 ETHnetwork2026-08-15
Withdrawal fee0.000000467 ETHnetwork2026-08-15
Operator fee0 ETHnetwork2026-08-15

A network fee is a blockchain-cost snapshot, not automatically an operator fee. A missing numeric value remains not verified.

Context

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.
Evidence

Source records

Direct operator documentation is listed without tracking parameters.