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.
Linea 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.
XRP is classified as a native asset for this route. XRP uses a network-specific contract asset on BNB Chain. The recorded BNB Chain representation uses 18 decimal places. Native XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
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 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 Linea; using a destination that is not valid for BNB Chain; 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. 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 XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
Linea 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 AVAX on Linea to XRP 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.
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.
XRP is a contract representation on BNB Chain with 18 decimals at 0x1D2F0da169ceB9fC7B3144628dB156f3F6c60dBE. BNB, not XRP, 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 XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
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 XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
AVAX is the deposited native-asset input; XRP 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. 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 XRP Ledger receipt can require a destination tag at a shared account; a tokenized XRP output instead follows the destination contract.
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 BNB Chain, can prevent detection or delivery. Match both network labels and representations to the active route.
Requirements are checked for the live AVAX Linea to XRP 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.
