Bridge WETH from Sui to Base

FromSui
ToBase
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 → Base

Asset

WETH

Source gas

SUI

Destination gas

ETH

How the Sasquatch deposit route works

1. Select the source

Choose the WETH asset and Sui network you currently hold.

2. Review the route

Check the estimated output, fees, timing, and Base 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 Base: 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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. Sui and Base 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.

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

WETH keeps its ticker while changing ledgers

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. The Sui side is contract-tracked rather than a native gas balance. WETH is classified as a wrapped asset for this route. WETH uses a wrapped contract asset on Base. The recorded Base representation uses 18 decimal places. The Base side is contract-tracked rather than a native gas balance. WETH leaves as a wrapped contract asset. WETH arrives as a wrapped contract asset.

Sui to Base bridge mistakes

Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Base; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable; treating a wrapped token as the native gas asset. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. 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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 WETH → WETH

Sui account, object, transaction-effect, and fee activity remain public, and Base wallet, token-transfer, contract, log, and gas activity remain public. For this WETH on Sui to WETH on Base 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 WETH deposit and WETH receipt
  • Compare standard and Private Route options for Sui → Base
  • Shows what remains public on Sui and Base before you deposit
Check Private Route availability →

Related routes

Sui to Base 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 WETH representation leaves Sui?

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

What WETH representation arrives on Base?

WETH is a contract representation on Base with 18 decimals at 0x4200000000000000000000000000000000000006. ETH, not WETH, pays gas unless both symbols are the same. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. WETH arrives as a token contract balance. It may need an explicit unwrap before becoming native ETH and cannot itself pay transaction gas.

Does the same WETH ticker guarantee the same ledger form?

No. This bridge keeps the asset intent while moving between a WETH wrapped token and a WETH wrapped 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. A Base receipt belongs to the Base L2 balance and token contract, not Ethereum L1; later activity needs ETH specifically on Base. 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 Base can prevent normal detection or receipt.

Can I bridge WETH from Sui to Base without KYC?

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