What BGB represents
Bitget Token (BGB) is available in network-specific native or token forms. Bitget Token belongs to the token category and must be verified through its network-specific native label or contract representation.
Review BGB network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Bitget Token (BGB)
Type
token
Available networks
1
Native networks
Contract token
Route support
Not currently available
Bitget Token (BGB) is available in network-specific native or token forms. Bitget Token belongs to the token category and must be verified through its network-specific native label or contract representation.
Bitget Token belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Ethereum; network gas remains a separate native balance.
Ethereum (contract)
Confirm the BGB network, contract or native label, and receiving address before using a route. Do not identify BGB solely by ticker; verify the asset and network representation. BGB can use different contracts on different networks.
Sasquatch does not currently list a transaction route for Bitget Token. Asset metadata is not proof of a live provider route.
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.
BGB is contract-based on Ethereum. Use the exact route representation rather than the ticker alone.
No native origin is recorded in this registry. Network gas is paid with each chain's native asset, not automatically with BGB.
Ethereum
Sasquatch does not currently list a transaction route for Bitget Token.
Confirm the BGB network, contract or native label, and receiving address before using a route. Do not identify BGB solely by ticker; verify the asset and network representation.