Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Linea. The recorded Linea representation uses 8 decimal places. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that 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.
WBTC is a custodial tokenized Bitcoin representation on smart-contract networks. Its transfers use token contracts and approvals rather than native Bitcoin inputs and outputs. On this route WBTC 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.
WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Arbitrum. The recorded Arbitrum representation uses 18 decimal places. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
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 WBTC on Linea to WETH 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.
WBTC is a contract representation on Linea with 8 decimals at 0x3aAB2285ddcDdaD8edf438C1bAB47e1a9D05a9b4. ETH, not WBTC, 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
WETH is a contract representation on Arbitrum with 18 decimals at 0x82aF49447D8a07e3bd95BD0d56f35241523fBab1. ETH, not WETH, 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. On receipt, WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
WBTC is the deposited wrapped-asset input; WETH is the quoted token output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.
No. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that 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. WBTC is token-tracked and can need approval before transfer.
Requirements are checked for the live WBTC Linea to WETH 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.
