Avalanche uses EVM account addresses and AVAX for source gas. Solana uses Solana accounts, transaction signatures, and SOL for destination activity. A 0x address is not a valid substitute for the Solana receiving address shown by the route. AVAX uses native AVAX on the source; SOL uses native SOL on Solana.
Base58-encoded Solana account address A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native. A compatible wallet may create or use an associated token account, and SOL—not SOL unless it is SOL—pays later Solana fees.
AVAX is the native gas asset for Avalanche. AVAX is a native source balance. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits.
Route-specific mistakes include sending on a network other than Avalanche; using a destination that is not valid for Solana; running out of AVAX before the source transaction is submitted; assuming evm and solana addresses are interchangeable. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. 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. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
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. 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.
Solana is classified as a native asset for this route. SOL uses a native asset on Solana. Native SOL exists on one recorded origin network; other network forms require representation checks. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
Avalanche wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this AVAX on Avalanche to SOL on Solana path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x account address and destination-side Base58-encoded Solana account address; it does not hide either chain's public records.
No. The destination must be a Solana-compatible address. Base58-encoded Solana account address
Native SOL is credited as a native balance. SOL is used for later Solana activity.
AVAX is listed as the native representation on Avalanche; AVAX is used for network gas. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. 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.
SOL is listed as the native representation on Solana; SOL is used for network gas. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
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 SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
AVAX is the deposited native-asset input; SOL 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. An Avalanche source route uses C-Chain Snowman execution and AVAX gas; X-Chain or P-Chain balances are not valid C-Chain deposits. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. Native SOL receipt uses a Solana address and can fund later fees; wrapped SOL uses an SPL token account and tokenized SOL elsewhere is not native.
Requirements are checked for the live AVAX Avalanche to SOL Solana 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.
