POL (ex-MATIC) is classified as a governance or utility token for this route. POL uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 18 decimal places. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules.
Arbitrum inclusion and its ethereum settlement are distinct from final receipt on BNB Chain. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays destination-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Arbitrum. EVM 0x account address On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.
Arbitrum and BNB Chain can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories. The recorded settlement context includes ethereum, so L1 and L2 confirmation behavior should not be assumed identical.
Route-specific mistakes include sending on a network other than Arbitrum; using a destination that is not valid for BNB Chain; running out of ETH before the source transaction is submitted. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and BNB Chain wallet, token-transfer, contract, log, and gas activity remain public. For this POL on Arbitrum to AVAX on BNB Chain path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side EVM 0x account address; it does not hide either chain's public records.
POL is a contract representation on Arbitrum with 18 decimals at 0x044d8e7F3A17751D521efEa8CCf9282268fE08CC. ETH, not POL, pays gas unless both symbols are the same. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules.
AVAX is a contract representation on BNB Chain with 18 decimals at 0x1CE0c2827e2eF14D5C4f29a091d735A204794041. BNB, not AVAX, pays gas unless both symbols are the same. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. On receipt, Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
POL is the deposited token input; AVAX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native POL can pay Polygon PoS gas, while a POL-labelled contract on another network uses that chain’s gas and token-transfer rules. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. A BNB Smart Chain receipt uses the BEP-20 contract or native BNB balance selected by the route; later token movement needs BNB gas. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
ETH is the native gas asset for Arbitrum. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. POL is token-tracked and can need approval before transfer.
Sending POL on a network other than Arbitrum, or using an address that is not valid for BNB Chain, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live POL Arbitrum to AVAX BSC quote. Verification requirements can depend on the provider, amount, jurisdiction, and current route. Sasquatch does not verify this route as universally no-KYC; check the live flow before continuing.
