Move from a Solana account into Avalanche EVM
Solana uses Solana accounts and SOL for source fees, while Avalanche uses an EVM 0x account and AVAX for destination gas. Confirm the destination token contract and do not paste a Solana address into the EVM destination field. WBTC is read from its Solana mint or native account, while USDC arrives at the quoted Avalanche native or contract representation.
WBTC mint and SOL fee checks
Base58-encoded Solana account address SOL is the native gas asset for Solana. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. WBTC leaves through a custodial wrapper contract with token approval and source-chain gas; no native Bitcoin UTXO is spent by that transfer. The mint/account selected by the quote must match the source wallet balance.
Avalanche contract and 0x receiving checks
EVM 0x account address AVAX is the native gas asset for Avalanche. 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. A Solana address cannot receive this EVM-side output.
Receiving stablecoin USDC
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.
WBTC unwrap or exchange input check
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 Solana. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.
Mistakes specific to WBTC Solana to USDC Avalanche
Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Avalanche; running out of SOL before the source transaction is submitted; assuming solana and evm addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract; treating a wrapped token as the native gas asset. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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.
WBTC input identity and handling
Wrapped Bitcoin is classified as a wrapped asset for this route. WBTC uses a wrapped contract asset on Solana. The Solana 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.
USDC output identity and receiving
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.