Direction
Ethereum → Avalanche
Asset
WBTC
Source gas
ETH
Destination gas
AVAX
Choose the WBTC asset and Ethereum network you currently hold.
Check the estimated output, fees, timing, and Avalanche destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
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 and Avalanche can use the same 0x address syntax, but they are separate networks with different chain identifiers, gas balances, token contracts, and transaction histories.
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Avalanche. The recorded Avalanche representation uses 8 decimal places. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
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.
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.
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.
Route-specific mistakes include sending on a network other than Ethereum; using a destination that is not valid for Avalanche; 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 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
Ethereum 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 Ethereum to WBTC 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 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.
WBTC is a contract representation on Avalanche with 8 decimals at 0x50b7545627a5162F82A992c33b87aDc75187B218. AVAX, not WBTC, 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. WBTC arrives as a wrapper-contract token and must not be sent onward to a native Bitcoin address without an explicit unwrap or bridge path.
No. This bridge keeps the asset intent while moving between a WBTC wrapped token and a WBTC wrapped token. Match the source and output details in the live quote.
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 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 bridge output does not automatically fund every later gas need.
EVM 0x account address Do not substitute a Ethereum address merely because a wallet displays both networks.
Sending on a network other than Ethereum, selecting a representation not listed by the quote, or entering an address invalid for Avalanche can prevent normal detection or receipt.
Requirements are checked for the live WBTC Ethereum to 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.
