Bridge SOL from Solana to Sui

FromSolana
ToSui
ENTER AMOUNT
Squatch Guard
Before a deposit order moves forward, Squatch Guard checks the amount, asset, network, and active quote window against the order details.

Direction

Solana → Sui

Asset

SOL

Source gas

SOL

Destination gas

SUI

How the Sasquatch deposit route works

1. Select the source

Choose the SOL asset and Solana network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Sui destination network.

3. Create the order

Open the live route and follow the exact deposit instructions.

4. Track delivery

Use the receipt and status page until the destination funds arrive.

What you need to know

Solana to Sui: object and account boundary

A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Solana and Sui use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.

Sui coin-object and SUI gas requirements

SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Coin objects and Move types are not EVM token contracts.

SOL input versus SOL output representation

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. 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.

SOL keeps its ticker while changing ledgers

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. Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Sui. The recorded Sui representation uses 8 decimal places. The Sui side is contract-tracked rather than a native gas balance. Native SOL exists on one recorded origin network; other network forms require representation checks. SOL leaves as a native asset. SOL arrives as a network-specific contract asset. The ticker remains the same while the ledger representation changes across the route.

Solana to Sui bridge mistakes

Route-specific mistakes include sending on a network other than Solana; using a destination that is not valid for Sui; running out of SOL before the source transaction is submitted; assuming solana and other addresses are interchangeable. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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.

Private Route for SOL → SOL

Solana account, token, program, signature, and fee activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this SOL on Solana to SOL on Sui 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 Sui hexadecimal account address with an object-based asset model; it does not hide either chain's public records.

  • Reduces the obvious link between the SOL deposit and SOL receipt
  • Compare standard and Private Route options for Solana → Sui
  • Shows what remains public on Solana and Sui before you deposit
Check Private Route availability →

Related routes

Solana to Sui FAQs

Which side uses Sui coin objects and SUI gas?

Sui is the Sui side. Its Move coin types, address, objects, and SUI gas do not transfer as EVM contract metadata.

What SOL representation leaves Solana?

SOL is listed as the native representation on Solana; SOL is used for network gas. A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. 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.

What SOL representation arrives on Sui?

SOL is a contract representation on Sui with 8 decimals at 0xb7844e289a8410e50fb3ca48d69eb9cf29e27d223ef90353fe1bd8e27ff8f3f8::coin::COIN. SUI, not SOL, pays gas unless both symbols are the same. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. 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.

Does the same SOL ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a native SOL and a SOL contract token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Solana source signs over accounts or token accounts, identifies SPL assets by mint, and spends SOL for transaction fees. A Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. The bridge output does not automatically fund every later gas need.

What destination address should be used?

Sui hexadecimal account address with an object-based asset model Do not substitute a Solana address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

Sending on a network other than Solana, selecting a representation not listed by the quote, or entering an address invalid for Sui can prevent normal detection or receipt.

Can I bridge SOL from Solana to Sui without KYC?

Requirements are checked for the live SOL Solana to Sui 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.

View all bridge FAQs →