It spends discrete UTXOs rather than debiting an account balance. Input selection creates outputs and often change, confirmation depth matters to the provider, and a native receiving address must match the Bitcoin address types accepted by the active route. The deposit is a Bitcoin transaction funded by selected inputs; BTC network fees and change outputs are part of the source record before AVAX can be delivered on Avalanche.
Native BTC is a Bitcoin UTXO asset with confirmations and Bitcoin address rules. Tokenized or wrapped Bitcoin on a smart-contract chain follows a contract ledger instead of the native UTXO graph. The live route must identify native BTC explicitly; a BTC ticker on another chain can represent a wrapped or bridged token.
The provider sets the required Bitcoin confirmation depth. 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 confirmations and Avalanche transaction finality are separate milestones.
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; confusing native BTC with wrapped or tokenized Bitcoin. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. 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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Avalanche is classified as a native asset for this route. AVAX uses a native asset on Avalanche. The recorded Avalanche representation uses 18 decimal places. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
Bitcoin is classified as a UTXO-native asset for this route. BTC uses a native asset on Bitcoin. Native BTC exists on one recorded origin network; other network forms require representation checks. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations.
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.
The Bitcoin side uses native BTC and the UTXO ledger. Native BTC is a Bitcoin UTXO asset with confirmations and Bitcoin address rules. Tokenized or wrapped Bitcoin on a smart-contract chain follows a contract ledger instead of the native UTXO graph.
The provider waits for its required source confirmation depth. The account-chain transaction and the Bitcoin transaction are separate records.
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.
BTC is listed as the native representation on Bitcoin; BTC is used for network gas. A Bitcoin source spends UTXOs, creates a fee-bearing transaction and possible change, and waits for the route provider’s confirmation depth. A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations.
AVAX is listed as the native representation on Avalanche; AVAX is used for network gas. 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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
A native BTC deposit spends selected UTXOs, pays a BTC miner fee, can create change, and advances through Bitcoin confirmations. On receipt, Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance.
BTC is the deposited native-asset input; AVAX is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
Requirements are checked for the live BTC Bitcoin to AVAX 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.
