Direction
Bitcoin → Avalanche
Asset
BTC → AVAX
Source gas
BTC
Destination gas
AVAX
Choose the BTC asset and Bitcoin 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.
Bitcoin uses a UTXO source model while Avalanche uses a non-UTXO destination model. Native Bitcoin deposits require a supported Bitcoin address, confirmation-aware input handling, and attention to change outputs; an EVM token labeled BTC or WBTC is not native BTC.
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.
Bitcoin is a L1 Bitcoin Script network in the Bitcoin ecosystem. BTC pays source-side network gas on Bitcoin. Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth.
The live quote lists the exact Bitcoin input asset and Avalanche output representation. A shared ticker is not proof of a shared contract, native ledger, decimals, or wallet support.
Route-specific mistakes include sending on a network other than Bitcoin; using a destination that is not valid for Avalanche; running out of BTC before the source transaction is submitted; assuming bitcoin and evm addresses are interchangeable. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. 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.
Bitcoin UTXO inputs, outputs, change, and confirmation history remain public, and Avalanche wallet, token-transfer, contract, log, and gas activity remain public. For this BTC on Bitcoin to AVAX on Avalanche path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats and destination-side EVM 0x account address; it does not hide either chain's public records.
Bitcoin is the UTXO source and BTC fees apply before the provider credits Avalanche. Tokenized BTC on an account chain is not the same ledger asset.
The live route lists assets supported in this direction. Confirm that the selected source representation has an explicit Avalanche output before depositing.
A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. 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 Bitcoin address merely because a wallet displays both networks.
Sending on a network other than Bitcoin, 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 BTC Bitcoin 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.
