What AVAX represents
Avalanche (AVAX) is available in network-specific native or token forms. AVAX is native to the Avalanche primary network and pays C-Chain gas. An AVAX-labeled contract on another smart-contract network is tokenized AVAX rather than the native C-Chain coin.
Native AVAX origin
AVAX is recorded as native on Avalanche. Native status describes the ledger balance and gas behavior on that network, not every token carrying the ticker.
AVAX forms away from the origin
Contract forms are recorded on Polygon, BNB Chain, Linea, Solana. Each form needs its own address, wallet, and network check.
AVAX network-by-network inventory
Avalanche (native), Polygon (contract), BNB Chain (contract), Linea (contract), Solana (contract)
AVAX 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 AVAX without a network mismatch
Confirm the AVAX network, contract or native label, and receiving address before using a route. Do not identify AVAX solely by ticker; verify the asset and network representation. Native AVAX and token representations on other networks are not interchangeable.
Routes arriving as AVAX
ARB → AVAX, BNB → AVAX, BTC → AVAX, DAI → AVAX, DOGE → AVAX, ETH → AVAX, HYPE → AVAX, LINK → AVAX, OP → AVAX, POL → AVAX
Routes spending AVAX
AVAX → ARB, AVAX → BNB, AVAX → BTC, AVAX → DAI, AVAX → DOGE, AVAX → ETH, AVAX → HYPE, AVAX → LINK, AVAX → OP, AVAX → POL
AVAX 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.