Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
Ethereum source execution occurs on L1, while Arbitrum delivery occurs on a separate L2 ledger that settles to ethereum. ETH pays source gas and ETH is the destination gas asset; identical-looking wallet addresses do not merge the balances or transaction histories.
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 Ethereum. 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.
POL (ex-MATIC) is classified as a governance or utility token for this route. POL uses a network-specific contract asset on Arbitrum. The recorded Arbitrum representation uses 18 decimal places. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Ethereum. EVM 0x account address An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit.
Ethereum 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 Ethereum; 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 Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
Ethereum 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 Ethereum to POL 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 Ethereum at 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599. ETH, not WBTC, pays gas unless both symbols are the same. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
POL is a contract representation on Arbitrum with 18 decimals at 0x044d8e7F3A17751D521efEa8CCf9282268fE08CC. ETH, not POL, 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. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
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, On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
WBTC is the deposited wrapped-asset input; POL 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. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
No. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. 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 Ethereum. An Ethereum source pays L1 base and priority fees in ETH, and an ERC-20 input can require a separate approval before the route deposit. WBTC is token-tracked and can need approval before transfer.
Requirements are checked for the live WBTC Ethereum to POL 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.
