How Suibridge Settlement Differs by Transfer Direction: ETH
Suibridge settlement has two different completion points: Ethereum-to-Sui locks ETH before minting bridged ETH, while Sui-to-Ethereum burns that representation before releasing ETH through a claim on Ethereum.
- Outward: look for the bridged asset in the Sui recipient’s balance.
- Return: complete the Ethereum claim, then wait for its transaction to confirm.
On this Sui Bridge route, ETH enters Ethereum custody before a matching asset appears on Sui. The Suibridge cross-chain bridge is a concrete lock-and-mint example: custody on the source chain precedes delivery on the destination chain.
suibridge.cc is a cross-chain bridge for moving supported crypto assets between Ethereum and Sui.
When Is an Ethereum-to-Sui or Sui-to-Ethereum Transfer Settled?
Ethereum-to-Sui settlement ends with destination delivery; Sui-to-Ethereum settlement needs a further claim and Ethereum confirmation. In either direction, the bridge waits for source finality, authorization by Sui validators’ voting power, and execution on the destination chain.
For the outward trip, Ethereum locks ETH first. The bridge waits for a configurable depth of Ethereum block confirmations before validators authorize the Sui-side mint. The result is a bridged ETH representation in the recipient’s Sui balance. The confirmation depth can change because the validator committee sets it.
Take an illustrative round trip with one ETH. Before the outward transfer, the asset is ETH on Ethereum. After delivery, the holder has bridged ETH on Sui, while the original ETH remains in bridge custody. The Sui Foundation launch guide describes delivery without a manual Sui claim in most Ethereum-to-Sui cases and an Ethereum-account claim for the return direction.
On the way back, the holder sends the bridged ETH from Sui. That representation is burned, and the bridge waits for Sui transaction finality before validator authorization of the Ethereum release. The bridge implementation records a message, verified signatures and claim status per transfer key across supported routes; its Sui send path burns or escrows the outgoing coin.
A finalized Sui burn therefore leaves an outstanding Ethereum claim. The Sui balance has changed, but ETH has not yet reached the Ethereum recipient. The user must submit the claim with the Ethereum account and wait for that destination transaction to confirm. For a return transfer, treat the confirmed Ethereum release—not the Sui burn—as completion.
Related Questions
Does Bridging ETH Turn It Into SUI?
Bridging ETH produces a bridged ETH representation on Sui. ETH remains the asset being represented; SUI is a different token.
Is Suibridge Wormhole Portal Bridge?
Suibridge and Wormhole Portal Bridge use separate bridge infrastructure. A bridged asset’s origin matters when identifying what a wallet or DeFi app holds.
What Should You Ask Before the Next Transfer?
What Determines Suibridge Fees?
Fees depend on the route and the transactions required on each chain. Review the current quote before submitting.
Which Tokens Does Suibridge Support?
Supported tokens depend on the current route. Confirm the asset on both chains before sending it.
Which Wallets Work With Suibridge?
You need access to the source account and the destination account. A return claim also requires the Ethereum account.
How Do I Track a Delayed Suibridge Transfer?
Follow the source transaction, validator authorization and destination transaction separately. On a return, look for an outstanding Ethereum claim after the Sui burn finalizes.
Comments
Join the discussionNo comments yet. Be the first to comment.