Avalanche is classified as a native asset for this route. AVAX uses a native asset on Avalanche. The recorded Avalanche 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.
Avalanche source execution occurs on L1, while Linea delivery occurs on a separate L2 ledger that settles to ethereum. AVAX pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
Linea is a L2 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Linea. EVM 0x account address A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract.
BNB is classified as a native asset for this route. BNB uses a network-specific contract asset on Linea. The recorded Linea 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.
Avalanche is a L1 EVM network in the Avalanche ecosystem. AVAX pays source-side network gas on Avalanche. EVM 0x account address An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits.
Avalanche and Linea 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 Avalanche; using a destination that is not valid for Linea; running out of AVAX before the source transaction is submitted. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. 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 receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. Native BSC receipt can fund BNB gas, while externally bridged BNB arrives as a representation that needs the destination chain’s gas token.
Avalanche wallet, token-transfer, contract, log, and gas activity remain public, and Linea wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Avalanche to BNB on Linea 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 listed as the native representation on Avalanche; AVAX is used for network gas. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. 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 Linea with 18 decimals at 0xf5C6825015280CdfD0b56903F9F8B5A2233476F5. ETH, not BNB, pays gas unless both symbols are the same. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. 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. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. A Linea receipt is recorded on the zkEVM L2 before the related proof settles to Ethereum; later activity needs ETH on Linea and the Linea token contract. 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 native gas asset for Avalanche. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. AVAX is recorded as native on this source.
Sending AVAX on a network other than Avalanche, or using an address that is not valid for Linea, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live AVAX Avalanche to BNB Linea 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.
