Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on Linea. The recorded Linea representation uses 18 decimal places. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
This route crosses two L2 execution environments. Linea settles to ethereum, while Arbitrum settles to ethereum; each side keeps its own gas balance, token contracts, transaction hash, and settlement progress.
Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Arbitrum. EVM 0x account address An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately.
BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 18 decimal places. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Linea. EVM 0x account address A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones.
Linea and Arbitrum 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 Linea; using a destination that is not valid for Arbitrum; running out of ETH before the source transaction is submitted. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Linea wallet, token-transfer, contract, log, and gas activity remain public, and Arbitrum wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Linea to BNB on Arbitrum 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.
AVAX is a contract representation on Linea with 18 decimals at 0x5471ea8f739dd37E9B81Be9c5c77754D8AA953E4. ETH, not AVAX, pays gas unless both symbols are the same. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
BNB is a contract representation on Arbitrum with 18 decimals at 0x20865e63B111B2649ef829EC220536c82C58ad7B. ETH, not BNB, pays gas unless both symbols are the same. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. On receipt, Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
AVAX is the deposited native-asset input; BNB is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. An Arbitrum receipt appears on the Nitro L2 ledger under an Arbitrum token contract or native ETH balance; later spending needs Arbitrum ETH while L1 settlement continues separately. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
ETH is the native gas asset for Linea. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. AVAX is token-tracked and can need approval before transfer.
Sending AVAX on a network other than Linea, or using an address that is not valid for Arbitrum, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live AVAX Linea to BNB Arbitrum 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.
