What BNB represents
BNB (BNB) is available in network-specific native or token forms. BNB pays gas on BNB Smart Chain and is native within the BNB ecosystem. A BEP-20 or externally bridged BNB representation must be distinguished from BNB used directly for BSC gas.
Native BNB origin
BNB is recorded as native on BNB Chain, opBNB. Native status describes the ledger balance and gas behavior on that network, not every token carrying the ticker.
BNB forms away from the origin
Contract forms are recorded on Ethereum, Arbitrum, Polygon, Linea, zkSync Era, Solana. Each form needs its own address, wallet, and network check.
BNB network-by-network inventory
BNB Chain (native), Ethereum (contract), Arbitrum (contract), Polygon (contract), Linea (contract), zkSync Era (contract), Solana (contract), opBNB (native)
BNB decimal formats differ
Recorded representations use 2 decimal formats. A receiving application must read the destination contract metadata instead of assuming the source precision applies.
Receiving BNB without a network mismatch
Confirm the BNB network, contract or native label, and receiving address before using a route. Do not identify BNB solely by ticker; verify the asset and network representation. Native BNB and token representations on other networks are not interchangeable.
Routes arriving as BNB
ARB → BNB, AVAX → BNB, BTC → BNB, DAI → BNB, DOGE → BNB, ETH → BNB, HYPE → BNB, LINK → BNB, OP → BNB, POL → BNB
Routes spending BNB
BNB → ARB, BNB → AVAX, BNB → BTC, BNB → DAI, BNB → DOGE, BNB → ETH, BNB → HYPE, BNB → LINK, BNB → OP, BNB → POL
BNB privacy and wallet linking
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.