Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Bridge SOL from Sui to Ethereum

FromSui
ToEthereum
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

Sui → Ethereum

Asset

SOL

Source gas

SUI

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the SOL asset and Sui network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Ethereum 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

Sui to Ethereum: object and account boundary

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. Sui and Ethereum 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 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. Solana is classified as a native asset for this route. SOL uses a network-specific contract asset on Ethereum. The recorded Ethereum representation uses 9 decimal places. The Ethereum 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 network-specific contract asset. SOL arrives as a network-specific contract asset.

Sui to Ethereum bridge mistakes

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Ethereum; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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

Sui account, object, transaction-effect, and fee activity remain public, and Ethereum wallet, token-transfer, contract, log, and gas activity remain public. For this SOL on Sui to SOL on Ethereum path, Private Route is intended to reduce the direct visible relationship between activity around the source-side Sui hexadecimal account address with an object-based asset model and destination-side EVM 0x account address; 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 Sui → Ethereum
  • ✓Shows what remains public on Sui and Ethereum before you deposit
Check Private Route availability →

Related routes

Private SOL from Sui to Ethereum route explainerPrivacy limits and live availabilityNo-KYC and verification rulesProvider and region requirementsCan a bridge link source and destination wallets?FAQ answerWhat is cross-chain privacy?FAQ answerAre Ethereum swaps public?FAQ answerCan bridge transactions be traced?Privacy researchPrivate bridge security checklistPrivacy researchHow cross-chain transactions are trackedPrivacy research

Sui to Ethereum 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 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 source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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 Ethereum?

SOL is a contract representation on Ethereum with 9 decimals at 0xD31a59c85aE9D8edEFeC411D448f90841571b89c. ETH, not SOL, pays gas unless both symbols are the same. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. 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 SOL contract token and a SOL contract token. Match the source and output details in the live quote.

Which gas balances matter for this bridge?

A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. An Ethereum receipt is an L1 native ETH balance or ERC-20 contract event; later token movement can require ETH gas and a new approval for another contract. The bridge output does not automatically fund every later gas need.

What destination address should be used?

EVM 0x account address Do not substitute a Sui address merely because a wallet displays both networks.

What wrong-direction mistake can prevent delivery?

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

Can I bridge SOL from Sui to Ethereum without KYC?

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