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 sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
BNB Chain source execution occurs on L1, while Linea delivery occurs on a separate L2 ledger that settles to ethereum. BNB 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.
Ethereum is classified as a native asset for this route. ETH uses a native asset on Linea. The recorded Linea representation uses 18 decimal places. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB Chain is a L1 EVM network in the BNB Chain ecosystem. BNB pays source-side network gas on BNB Chain. EVM 0x account address A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20.
BNB Chain 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 BNB Chain; using a destination that is not valid for Linea; running out of BNB before the source transaction is submitted. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB Chain wallet, token-transfer, contract, log, and gas activity remain public, and Linea wallet, token-transfer, contract, log, and gas activity remain public. For this XRP on BNB Chain to ETH 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.
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 source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network.
ETH is listed as the native representation on Linea; ETH is used for network gas. 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. On receipt, Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
XRP is the deposited native-asset input; ETH is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Native XRP sending can require XRP Ledger address and destination-tag handling, while tokenized XRP uses the selected smart-contract network. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. 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. Determine whether ETH arrives as native destination gas or as a tokenized representation. Only the native balance can directly pay that network’s fees.
BNB is the native gas asset for BNB Chain. A BNB Smart Chain source uses BNB gas and BEP-20 contracts; a familiar 0x account does not turn a BEP-20 deposit into ERC-20. XRP is token-tracked and can need approval before transfer.
Sending XRP on a network other than BNB Chain, 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 XRP BSC to ETH 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.
