Sasquatch Exchange
TRADE
OrdersSupportAffiliatePrivate Swap

Swap SOL on Base to WETH on Sui

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

What you need to know

Base to Sui: object and account boundary

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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. Base 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 WETH 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

WETH wrapped-token output check

WETH is a contract wrapper for ETH. It can be transferred as a token but cannot replace the native gas balance required by the network. On this route WETH is the destination token on Sui. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to SOL Base to WETH Sui

Route-specific mistakes include sending on a network other than Base; using a destination that is not valid for Sui; running out of ETH before the source transaction is submitted; assuming evm and other addresses are interchangeable; treating a wrapped token as the native gas asset. 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

SOL input identity and handling

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

WETH output identity and receiving

WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Sui. The recorded Sui representation uses 8 decimal places. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Private Route for SOL → WETH

Base wallet, token-transfer, contract, log, and gas activity remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this SOL on Base to WETH on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side EVM 0x 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 WETH receipt
  • ✓Compare standard and Private Route options for Base → Sui
  • ✓Shows what remains public on Base and Sui before you deposit
Check Private Route availability →

Related routes

No-KYC and verification rulesPrivate SOL to WETH route explainerPrivacy limits and live availabilitySwap WETH to SOLReverse routeSolana (SOL)WETH (WETH)Base networkSui networkBrowse supported swap routes

Swap SOL on Base to WETH on Sui FAQs

How does the Sui coin-object side differ from the other network?

Sui uses Move coin types and objects with SUI gas. The other side follows EVM execution, so addresses and token identifiers are not interchangeable.

What exactly leaves Base as SOL?

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.

What exactly arrives on Sui as WETH?

WETH is a contract representation on Sui with 8 decimals at 0xaf8cd5edc19c4512f4259f0bee101a40d41ebed738ade5874359610ef8eeced5::coin::COIN. SUI, not WETH, 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. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Why does the SOL to WETH direction matter?

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. On receipt, WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

What changes between the source and destination asset roles?

SOL is the deposited native-asset input; WETH is the quoted token output. Source allowance or native-spend rules and destination wallet/representation checks are evaluated separately.

What should be matched before sending SOL?

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 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Can the wrapped asset pay native network gas?

No. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas. 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 Sui receipt creates or updates Move coin objects at a Sui address; later object operations require SUI gas rather than an EVM allowance.

Can I swap SOL on Base to WETH on Sui without KYC?

Requirements are checked for the live SOL Base to WETH 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 Help Center FAQs →