Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Arbitrum. The recorded Arbitrum 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.
Arbitrum inclusion and its ethereum settlement are distinct from final receipt on Ethereum. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
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 Arbitrum. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Ethereum is a L1 EVM network in the Ethereum ecosystem. ETH pays destination-side network gas on Ethereum. EVM 0x account address An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.
POL (ex-MATIC) is classified as a governance or utility token for this route. POL uses a network-specific contract asset on Ethereum. The Ethereum side is contract-tracked rather than a native gas balance. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
Arbitrum is a L2 EVM network in the Ethereum ecosystem. ETH pays source-side network gas on Arbitrum. EVM 0x account address On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval.
Arbitrum and Ethereum 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 Arbitrum; using a destination that is not valid for Ethereum; running out of ETH before the source transaction is submitted; treating a wrapped token as the native gas asset. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. 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 receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
Arbitrum wallet, token-transfer, contract, log, and gas activity remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Arbitrum to POL on Ethereum 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 Arbitrum with 8 decimals at 0x2f2a2543B76A4166549F7aaB2e75Bef0aefC5B0f. ETH, not WBTC, pays gas unless both symbols are the same. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. 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 Ethereum at 0x455e53cbb86018ac2b8092fdcd39d8444affc3f6. ETH, not POL, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract.
ETH is the native gas asset for Arbitrum. On an Arbitrum source, the Nitro sequencer records L2 execution before Ethereum settlement completes; ETH funds gas and ERC-20 inputs can need approval. WBTC is token-tracked and can need approval before transfer.
Requirements are checked for the live WBTC Arbitrum to POL Ethereum 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.
