Sui network

Sui is a L1 Move VM network in the Sui ecosystem. Review SUI gas, address requirements, supported assets, and available routes.

FromSui

ToArbitrum

ENTER AMOUNTSUI / SUI -> USDC / ARBITRUM

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: —

Network

Sui

Type

L1 • Move VM

Gas asset

SUI

Address format

other

Route support

Available

Supported assets

What you need to know

About Sui

Sui is a L1 Move VM network in the Sui ecosystem.

Sui Move VM execution model

It uses an object-centric Move execution model in which owned and shared objects participate in transactions. Sui addresses and coin objects are not EVM token contracts, and SUI is required for gas and storage-related execution. Wallet, address, fee, and finality assumptions must come from this network rather than an EVM default.

Sui address and wallet compatibility

Sui hexadecimal account address with an object-based asset model. Use a wallet that explicitly supports this network

Sui incoming and outgoing route map

8 outgoing bridge directions, 8 incoming bridge directions, and 1320 exact swap routes are currently represented. Each direction has separate source gas, destination address, and representation checks.

Recorded assets on Sui

ETH, SOL, SUI, USDC, USDT, WBTC, WETH are recorded for this network. Native balances and contract tokens must still be distinguished in the exact route.

Current provider mapping scope

Sui has one recorded provider mapping. Availability remains conditional on the exact asset pair, direction, amount, and current quote.

Sui official verification resources

Use the recorded explorer at https://suiscan.xyz/mainnet to verify network activity. Network documentation begins at https://sui.io/.

Mistakes specific to Sui

EVM token contracts do not apply on Sui. Keep SUI for destination gas.

Private Route

Sui account and object activity, transaction effects, token transfers, amounts, and timing can remain public under its Move-based execution model. Private Route can reduce direct linkage where available, but it does not remove public records. Availability depends on the exact asset, direction, amount, provider, and current route conditions.