Sui Bridge

Move Assets Between Ethereum and Sui

Sui Bridge is Sui's native, validator-secured protocol for moving supported assets between Ethereum Mainnet and Sui Mainnet in either direction.

Preview

Preview only
Ethereum tokenEthereum 0.00Preview
Base tokenBase 0.00Preview
Deposit · Ethereum → SuiNon-custodial bridge route
Base token Base
TypeBridge route
CustodyNon-custodial
Go to Swap
Scroll

Sui Bridge Protocol Architecture & Route Overview

Sui Bridge is the native bridging protocol built into Sui's core architecture: it locks supported assets on Ethereum and issues corresponding Move coin representations on Sui, with security enforced by Sui validators rather than a third-party guardian set.

Read more

In practice you connect an Ethereum wallet and a Sui wallet at the official bridge interface, pick a direction and asset, approve the ERC-20 allowance if needed, and sign. This page is an independent dashboard for reference only — it does not execute transfers and never touches your funds.

RouteEthereum Mainnet (chain ID 1) <-> Sui Mainnet
DepositFinalized Ethereum deposit, then mint on Sui
WithdrawBurn on Sui, then a manual Ethereum claim
GasETH on Ethereum, SUI on Sui
CustodyNon-custodial — your wallet signs
VerifyUse the official contracts; beware fake bridge sites
Sui Bridge

What is Sui Bridge?

Sui Bridge is a bidirectional, open-source bridge operated by Sui validators rather than an external network: an Ethereum asset is locked and an equivalent Move coin type is minted on Sui, while the return route burns that Sui representation and releases the escrowed Ethereum asset. Its validator-operated model differs from third-party routes such as Wormhole, which use a separate guardian set, as described in Sui’s mainnet launch. The documented supported assets are WBTC, LBTC, ETH, WETH, and USDT; another asset needs a different route. A global limiter caps rolling outbound value and individual transfer size, so a large transfer can be throttled by design.

How bridging works

Bridging uses lock-and-mint from Ethereum to Sui and burn-and-claim on the return route. For a deposit, tokens enter the Ethereum bridge contract, bridge nodes independently verify the finalized deposit, and a permissionless client collects stake-weighted ECDSA signatures from the Sui Bridge Committee and submits them to the destination. The Sui package checks the threshold using recoverable secp256k1 signatures, then mints the Sui asset; returning burns that representation and requires a manual Ethereum claim to release escrowed funds. An ERC-20 standard token needs a separate allowance approval, and that approval only needs to cover the amount being bridged. The Sui bridging documentation shows the complete flow.

Depositing to the destination

To deposit from Ethereum to Sui, connect both wallets, choose the asset and amount, confirm the recipient Sui address, approve the token allowance when the asset is an ERC-20, then sign the deposit. Bridge nodes verify it only after the Ethereum transaction finalizes, so minting follows Ethereum finality rather than a wallet confirmation toast; congestion on Ethereum can stretch the wait. Keep ETH for the approval and deposit gas, and keep a little SUI in the receiving wallet so you can use the bridged asset after it arrives. If the mint is missing, check the deposit transaction’s status on an Ethereum explorer before assuming failure.

Withdrawing back

To withdraw from Sui to Ethereum, burn the Sui-side asset, wait for the committee’s signatures to cover that burn, then submit the manual Ethereum claim that releases the escrowed tokens; the claim costs Ethereum gas. Burning alone does not complete the withdrawal, so do not resubmit the burn while it is pending. The outbound limiter can delay large withdrawals during high-volume periods, and the assets remain in escrow until the claim confirms on Ethereum.

Time and fees

Bridge fees are the chain-gas payments required by each transaction, not a flat quoted fee. A deposit uses Ethereum gas for the ERC-20 approval plus the deposit transaction; a withdrawal uses a Sui-side transaction plus Ethereum gas for the manual claim, usually the most expensive single step. Ethereum’s gas documentation explains the network-fee model; check the live estimate in your wallet before each signature because Ethereum gas varies over time. A third-party route can add a provider or relayer fee on top of gas, so read that quote line before confirming.

Is Sui Bridge safe?

Sui Bridge’s security model is stake-weighted signatures from a committee of Sui validators, while bridged assets remain in escrow during transit; its v1 code was audited by OtterSec and Zellic. An audit does not remove smart-contract, validator, wallet, chain-finality, or operational risk, and fake interfaces or malicious approvals add user-side risk. Before signing, verify the interface URL and the Ethereum bridge contract at 0xda3bD1fE1973470312db04551B65f401Bc8a92fD. The interface does not ask for a seed phrase or private key; a site that does is phishing.

Problems and fixes

Fix the network, gas, or transaction-state mismatch first: the Ethereum wallet must be on Mainnet (chain ID 1), not a testnet or L2, and a destination Sui wallet with zero SUI cannot use the bridged asset until funded, so keep a small SUI balance there. For a pending deposit, check whether the Ethereum transaction finalized before resubmitting anything; for a pending withdrawal, check whether the manual Ethereum claim was submitted after the Sui burn.

Sui FAQ

Is this the official Sui Bridge site?

No. This is an independent informational dashboard; it does not execute transfers or custody funds. Transfers happen at the official interface, which you should reach by typing the URL rather than clicking ads or search results.

How long does a Sui Bridge transfer take?

Deposits complete after the Ethereum transaction finalizes and the bridge committee’s signatures are collected. Withdrawals add a second step: after the Sui-side burn, submit the manual Ethereum claim and wait for that transaction to confirm.

How do I bridge from Ethereum to Sui?

Connect an Ethereum wallet and a Sui wallet, select WBTC, LBTC, ETH, WETH, or USDT, enter the amount and recipient, approve the ERC-20 allowance if prompted, then sign the deposit. The Move coin appears on Sui after the deposit is finalized and verified.

Do I need SUI before bridging to Sui?

Not to receive the bridged asset, but yes to use it: Sui actions require SUI for gas. Keep SUI in the destination wallet and ETH on Ethereum for approvals and a return claim.

Is Sui Bridge safe to use?

It uses stake-weighted signatures from Sui validators, and the v1 code was audited by OtterSec and Zellic, but an audit does not remove smart-contract, cross-chain, or phishing risk. Verify the site and contract before signing, and never enter a seed phrase.

Should I use the native bridge or a third-party one like Wormhole?

The native bridge is validator-operated and covers the core Ethereum <-> Sui route for its supported assets; third-party bridges use separate guardian or relayer networks and often support more chains and tokens. Choose by the asset and route, compare quoted fees, and use the native bridge primer for the design trade-offs.

Notes before you use Sui Bridge

Practitioner take: the native bridge is the straightforward path for Ethereum-to-Sui moves of its supported assets; the return trip is two transactions, not one.

Burning the Sui-side asset does not finish a withdrawal: the manual Ethereum claim releases the escrowed tokens and costs Ethereum gas.

Before signing, confirm the interface, contract, networks, recipient address, and gas balances in your own wallets.

Everything on this page was checked against Sui's published documentation and on-chain contract references, last reviewed 21 July 2026.

Independent reference — confirm the route in your own wallet.