ce5f72
ETH to Sui: Suibridge vs Wormhole by Source and Coin Type
For ETH on Ethereum mainnet, Suibridge is the usual route to Sui when your destination app accepts its ETH coin type. Sui validators secure the bridge…
The Hashbeam Desk··5 min read

For ETH on Ethereum mainnet, Suibridge is the usual route to Sui when your destination app accepts its ETH coin type. Sui validators secure the bridge, and that coin type is the one most Sui apps list. Your source chain and the exact coin type your app accepts can change the choice.
- ETH on Ethereum mainnet, with an app that accepts native bridged ETH: use the native bridge.
- ETH on another supported chain, or an app that specifies Wormhole ETH: use Wormhole Connect or Wormhole Portal Bridge.
- ETH held on an exchange: consider a direct Sui withdrawal if the exchange supports that asset and network.
Which route fits your ETH and Sui app?
Choose by source chain first, then by the coin type your app accepts. The native bridge connects Ethereum mainnet and Sui: it locks ETH on Ethereum and mints the matching token on Sui. For its supported ETH route, current cost estimate and transfer status, see Suibridge before sending.
Wormhole Connect reaches Sui from other supported chains; Wormhole Portal Bridge offers a direct website for Wormhole transfers. Their transfers rely on Wormhole’s Guardian network, while the native bridge relies on the Sui validator committee. That is a different trust model even when both routes begin with ETH on Ethereum. Sui’s bridging documentation describes the routes and their received tokens.
The received coin type is often the deciding detail. A Sui wallet can display two balances as “ETH” while their coin type addresses differ. A Sui protocol accepts the coin type specified by its market or deposit contract, not every token with an ETH label. Sending Wormhole-minted ETH toward a market that lists native bridged ETH leaves you holding a token that market cannot accept. Read the app’s supported coin type before choosing a bridge.
Say two users hold ETH on Ethereum mainnet, use the same Sui wallet and plan to deposit into the same lending app. One selects a market listing native bridged ETH, so the native bridge delivers the required coin. The other selects a market listing Wormhole ETH, so a Wormhole route fits instead. Only the market’s accepted coin type changed; that change reverses the route choice.
An exchange-held balance creates a third option. A direct withdrawal to Sui avoids an onchain bridge transaction from your Ethereum wallet, but the exchange must offer Sui withdrawals for ETH specifically. A “Sui network” option for SUI alone is insufficient. Confirm the ETH coin type the exchange delivers, its withdrawal fee and its processing estimate. The exchange controls the withdrawal until it reaches your wallet, so its support and timing are part of the choice.
Choose the native bridge when your ETH is on Ethereum mainnet and your Sui app lists its ETH coin type. Choose Wormhole Connect or Portal Bridge when your ETH starts on another supported chain or the app lists Wormhole’s coin type. If the ETH sits on a chain the chosen route cannot serve, move it to Ethereum mainnet first or find a supported route that delivers the coin type you need.
The Return Path Adds an Ethereum Claim
A return through the native bridge ends with a separate claim transaction on Ethereum. You first send the bridged ETH from Sui; after the bridge committee signs that transfer, the Ethereum claim releases the locked ETH. The claim needs Ethereum gas paid in ETH. Keep some ETH in the claiming wallet on Ethereum before leaving Sui, especially if you intend to bridge your entire balance back. The ETH you are claiming cannot pay for a transaction that must happen before those funds arrive. Sui’s bridge architecture explanation describes this separate claim.
That return cost matters most for a small transfer or a short stay on Sui. Compare the full round trip: source-chain gas, any route fee, Sui transaction gas and the eventual Ethereum claim. Wormhole routes and exchanges have their own return options and charges; inspect the actual return route instead of assuming the inbound route reverses at the same cost.
Related Questions
How long does bridging ETH to Sui take?
Ethereum-to-Sui delivery through the native bridge waits for Ethereum finality, roughly 13 minutes or two Ethereum epochs, before Sui-side processing completes. The exact arrival time can vary with Ethereum confirmation depth and bridge processing. Wormhole timing depends on its source chain and transfer route; an exchange adds its own withdrawal processing time.
What fees do I pay to bridge ETH to Sui?
From Ethereum mainnet, budget ETH for the source transaction and review the route’s displayed fee estimate. Wormhole may add a relay or route charge. An exchange withdrawal skips your wallet’s bridge gas but may charge a withdrawal fee. On Sui, later actions use SUI for gas unless an app sponsors them.
Do I need SUI before receiving bridged ETH?
A Sui wallet can receive bridged ETH without already holding SUI. To send it, swap it or deposit it into a protocol, you generally need SUI for transaction gas. Wormhole Connect can offer a SUI gas drop-off; review its charge and amount before relying on it.
Revisit the choice when your ETH moves to another chain or your target app changes its accepted coin type: the route should follow the new source and deliver the token the app actually accepts.