WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Optimism. The recorded Optimism 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. Optimism 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 Optimism. 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.
Arbitrum is classified as a governance or utility token for this route. ARB uses a network-specific contract asset on Arbitrum. The Arbitrum side is contract-tracked rather than a native gas balance. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
Optimism is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Optimism. EVM 0x account address An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay.
Optimism 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 Optimism; 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. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
Optimism 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 Optimism to ARB 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 Optimism with 18 decimals at 0x4200000000000000000000000000000000000006. ETH, not WETH, pays gas unless both symbols are the same. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. 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.
ARB is a contract representation on Arbitrum at 0x912ce59144191c1204e64559fe8253a0e49e6548. ETH, not ARB, 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
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, A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
WETH is the deposited token input; ARB is the quoted token 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. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. 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. A receiving wallet should show the exact ARB contract on the destination. Receipt does not fund ETH gas for later token movement.
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. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. 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 Optimism. An OP Mainnet source uses sequenced OP Stack execution and ETH gas; ordinary route processing is not the same as the canonical L2 withdrawal delay. WETH is token-tracked and can need approval before transfer.
Requirements are checked for the live WETH OP Mainnet to ARB 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.
