WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Linea. The recorded Linea representation uses 18 decimal places. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.
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.
WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. On this route WETH is the source token on Linea. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
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.
TRON is classified as a native asset for this route. TRX uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 6 decimal places. Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
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; treating a wrapped token as the native gas asset. A Linea source is executed on the zkEVM rollup and later proven to Ethereum; L2 inclusion and proof settlement are distinct source milestones. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. 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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
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 WETH on Linea to TRX 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.
WETH is a contract representation on Linea with 18 decimals at 0xe5D7C2a44FfDDf6b295A15c148167daaAf5Cf34f. ETH, not WETH, 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. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.
TRX is a contract representation on Arbitrum with 6 decimals at 0x2adefAC87331698F33AD2fBbbd313b444B890eaA. ETH, not TRX, 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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. On receipt, Native TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
WETH is the deposited token input; TRX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. 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 TRX receipt belongs to a Tron address and can support network resources; tokenized TRX on another ledger cannot supply Tron bandwidth or energy.
No. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. 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.
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. WETH is token-tracked and can need approval before transfer.
Requirements are checked for the live WETH Linea to TRX 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.
