Direction
Solana → Avalanche
Asset
AVAX
Source gas
SOL
Destination gas
AVAX
Choose the AVAX asset and Solana 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.
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. AVAX is read from its Solana mint or native account, while AVAX arrives at the quoted Avalanche native or contract representation.
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. 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. The mint/account selected by the quote must match the source wallet balance.
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. Native Avalanche receipt belongs on C-Chain and can fund later gas; an AVAX token on another chain remains a contract balance. A Solana address cannot receive this EVM-side output.
Avalanche is classified as a native asset for this route. AVAX uses a network-specific contract asset on Solana. The recorded Solana representation uses 8 decimal places. The Solana side is contract-tracked rather than a native gas balance. Native AVAX exists on one recorded origin network; other network forms require representation checks. 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 AVAX exists on one recorded origin network; other network forms require representation checks. AVAX leaves as a network-specific contract asset. AVAX arrives as a native asset. The ticker remains the same while the ledger representation changes across the route.
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. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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. 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.
Solana account, token, program, signature, and fee activity remain public, and Avalanche wallet, token-transfer, contract, log, and gas activity remain public. For this AVAX on Solana to AVAX on Avalanche path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Base58-encoded Solana account address and destination-side EVM 0x account address; it does not hide either chain's public records.
The source uses a Solana signature, mint or native account, and SOL fees. The destination uses a 0x account, AVAX gas, and the quoted EVM token contract or native balance.
AVAX is a contract representation on Solana with 8 decimals at KgV1GvrHQmRBY8sHQQeUKwTm2r2h8t4C8qt12Cw1HVE. SOL, not AVAX, pays gas unless both symbols are the same. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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.
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.
No. This bridge keeps the asset intent while moving between a AVAX contract token and a native AVAX. Match the source and output details in the live quote.
A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 Solana address merely because a wallet displays both networks.
Sending on a network other than Solana, 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 AVAX Solana 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.
