Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Optimism. The recorded Optimism 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.
USDC is an issued dollar-oriented stablecoin with canonical, native, and bridged variants across networks. Contract events and issuer controls differ from a network-native gas asset. The destination wallet must support the exact Avalanche representation. The route converts a wrapped-asset source into a stablecoin balance; the destination ticker alone is not a contract check.
Optimism inclusion and its ethereum settlement are distinct from final receipt on Avalanche. The live route, rather than a generic rollup withdrawal assumption, determines the provider path and timing for this direction.
USDC is classified as a stablecoin for this route. USDC uses a network-specific contract asset on Avalanche. The Avalanche side is contract-tracked rather than a native gas balance. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
Avalanche is a L1 EVM network in the Avalanche ecosystem. AVAX pays destination-side network gas on Avalanche. EVM 0x account address An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract.
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.
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 Optimism. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Route-specific mistakes include sending on a network other than Optimism; using a destination that is not valid for Avalanche; running out of ETH before the source transaction is submitted; selecting a stablecoin by ticker without checking its network contract; 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
Optimism wallet, token-transfer, contract, log, and gas activity remain public, and Avalanche wallet, token-transfer, contract, log, and gas activity remain public. For this WBTC on Optimism to USDC on Avalanche 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 Optimism with 8 decimals at 0x0555E30da8f98308EdB960aa94C0Db47230d2B9c. ETH, not WBTC, 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. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer.
USDC is a contract representation on Avalanche at 0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e. AVAX, not USDC, pays gas unless both symbols are the same. An Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
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, The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
WBTC is the deposited wrapped-asset input; USDC is the quoted stablecoin 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 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 Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract. The wallet must support the destination USDC native label or contract. Receipt does not automatically supply the destination network’s gas asset.
USDC must match the quoted Avalanche representation. A ticker or target price is not enough to identify a token contract.
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 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 Avalanche destination must be a C-Chain-compatible account; native AVAX can fund later C-Chain gas, while token receipt uses the quoted C-Chain contract.
Requirements are checked for the live WBTC OP Mainnet to USDC Avalanche 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.
