Avalanche is classified as a native asset for this route. AVAX uses a quote-selected representation. Native AVAX exists on one recorded origin network; other network forms require representation checks. On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead.
Bitcoin is classified as a UTXO-native asset for this route. BTC uses a quote-selected representation. Native BTC exists on one recorded origin network; other network forms require representation checks. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
AVAX leaves as a quote-selected representation. BTC arrives as a quote-selected representation.
Avalanche wallet, token-transfer, contract, log, and gas activity remain public, and Bitcoin UTXO inputs, outputs, change, and confirmation history remain public. For this AVAX on Avalanche to BTC on Bitcoin path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Native Bitcoin address supported by the route, including network-specific bech32 or legacy formats; it does not hide either chain's public records.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. On receipt, Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
AVAX is the deposited native-asset input; BTC is the quoted native-asset output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.
On Avalanche C-Chain, native AVAX funds both the transfer value and gas; on another chain, an AVAX-labelled contract behaves as a token input instead. Match the source network shown by the quote. Confirm the destination network in the quote. Native BTC must arrive at a provider-accepted Bitcoin address and becomes a UTXO after broadcast; an EVM address is not a native BTC destination.
Requirements are checked for the live AVAX Avalanche to BTC Bitcoin 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.
