Swap WETH to SUI

FromEthereum
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.
SUI / USD
Price
24h
High
Low
Vol

What you need to know

WETH input identity and handling

WETH is classified as a wrapped asset for this route. WETH uses a quote-selected representation. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.

SUI output identity and receiving

Sui is classified as a native asset for this route. SUI uses a quote-selected representation. Native SUI exists on one recorded origin network; other network forms require representation checks. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

WETH unwrap or exchange input 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 source token. Its token balance, approvals, and contract transfer behavior are separate from the native coin used for network gas.

Mistakes specific to WETH to SUI

Verify both asset identities, the selected network, current deposit instructions, and the receiving representation.

WETH source handling versus SUI receipt

WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Private Route for WETH → SUI

the selected source network addresses, transfers, amounts, fees, and timing remain public, and Sui account, object, transaction-effect, and fee activity remain public. For this WETH on the selected source network to SUI on Sui path, Private Route is intended to reduce the direct visible relationship between activity around the source-side the selected source network 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 WETH deposit and SUI receipt
  • Compare standard and Private Route options for the selected source network → Sui
  • Shows what remains public on the selected source network and Sui before you deposit
Check Private Route availability →

Related routes

Swap WETH to SUI FAQs

Why does the WETH to SUI direction matter?

WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. On receipt, Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

What changes between the source and destination asset roles?

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

What should be matched before sending WETH?

WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer. Match the source network shown by the quote. Confirm the destination network in the quote. Native SUI receipt creates Sui coin objects that can fund later gas. A smart-contract token outside Sui does not become a native object.

Can the wrapped asset pay native network gas?

No. WETH leaves through a wrapper contract and needs native chain gas. A WETH token balance cannot pay the gas required to submit its own transfer.

Can I swap WETH on Wrapped Ether to SUI on Sui without KYC?

Requirements are checked for the live WETH Wrapped Ether to SUI 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 →