Direction
Base → Solana
Asset
SOL
Source gas
ETH
Destination gas
SOL
Choose the SOL asset and Base network you currently hold.
Check the estimated output, fees, timing, and Solana destination network.
Open the live route and follow the exact deposit instructions.
Use the receipt and status page until the destination funds arrive.
Base uses EVM account addresses and ETH 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. SOL uses SOL contract token 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.
ETH is the native gas asset for Base. SOL is contract-tracked and can require an allowance before transfer. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger.
Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Base. The recorded Base representation uses 9 decimal places. The Base side is contract-tracked rather than a native gas balance. Native SOL exists on one recorded origin network; other network forms require representation checks. 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. SOL leaves as a network-specific contract asset. SOL 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 Base; using a destination that is not valid for Solana; running out of ETH before the source transaction is submitted; assuming evm and solana addresses are interchangeable. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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.
Base wallet, token-transfer, contract, log, and gas activity remain public, and Solana account, token, program, signature, and fee activity remain public. For this SOL on Base 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. Base58-encoded Solana account address ETH pays the EVM source transaction, while SOL is used for later Solana activity.
SOL is a contract representation on Base with 9 decimals at 0x311935Cd80B76769bF2ecC9D8Ab7635b2139cf82. ETH, not SOL, pays gas unless both symbols are the same. A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. Native SOL leaves a Solana account through a signed transaction and pays the fee; wrapped or tokenized SOL uses a token account or external contract 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.
No. This bridge keeps the asset intent while moving between a SOL contract token and a native SOL. Match the source and output details in the live quote.
A Base source transaction is sequenced on the OP Stack rollup and later settles to Ethereum; Base ETH and Base token approvals remain on the L2 ledger. A Solana receipt uses a native SOL balance or SPL token account identified by mint; later token movement and account creation use SOL fees. The bridge output does not automatically fund every later gas need.
Base58-encoded Solana account address Do not substitute a Base address merely because a wallet displays both networks.
Sending on a network other than Base, selecting a representation not listed by the quote, or entering an address invalid for Solana can prevent normal detection or receipt.
Requirements are checked for the live SOL Base to 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.
