An outbound Sui Bridge transfer has two user transactions: a Sui-side send or burn and an Ethereum-side claim. The first creates a bridge message; the second releases the locked Ethereum asset. Stopping after the Sui transaction leaves the withdrawal incomplete.
Open the Sui-to-Ethereum withdrawal route with both a Sui wallet and the intended Ethereum claim account prepared.
Which assets can return through the native route?
Only coins mapped by the current Sui Bridge token list can use the native return path. The live interface lists ETH, WETH, USDT, WBTC, and LBTC. The Sui coin type must correspond to the Sui Bridge representation, not another bridge’s token with the same ticker.
Verify the mapping before the Sui coin is burned or locked.
Which address should receive on Ethereum?
Enter the intended Ethereum account and confirm that it is controlled by the wallet that will complete the claim. Ethereum addresses are 20 bytes, while Sui addresses are 32 bytes; the interface should not be allowed to infer the wrong side from a copied string.
Check the full recipient in the Sui transaction review.
What happens in the Sui-side transaction?
The bridge package consumes or records the Sui coin, assigns a sequence number, stores the target chain and address, applies the route limiter, and emits the transfer evidence. The Sui bridge module documents send functions and token-transfer records.
A successful receipt proves initiation, not Ethereum delivery.
How do validators authorize the withdrawal?
Bridge committee nodes observe the Sui event and sign the corresponding message with their bridge keys. The claim transaction includes enough weighted signatures for Ethereum verification.
Duplicate, unknown, or blocklisted signers should not contribute valid voting power under the documented committee logic.
When does the withdrawal become claimable?
It becomes claimable when the bridge has collected sufficient approval and the outbound limiter permits execution. The interface transaction page should distinguish signature collection, limit delay, and ready-to-claim state.
Do not submit another Sui withdrawal while the first message is merely waiting for approval or capacity.
Why is the Ethereum claim manual?
The user sends the signatures and message data to the Ethereum bridge contract and pays Ethereum gas. The mainnet launch guide explicitly states that Sui-to-Ethereum users need to claim manually.
This design makes control of the Ethereum wallet and claim funding part of the route requirements.
How much ETH is needed for the claim?
Keep enough ETH for a contract call that verifies committee signatures and releases the asset. Gas changes with Ethereum conditions and claim calldata. Estimate immediately before execution rather than relying on a static number.
The bridged asset itself cannot always pay gas before it has been claimed.
What should the claim transaction be checked against?
Compare the Ethereum contract, message sequence, source and target chains, token ID, amount, sender, and recipient with the Sui event. Use the official transaction page and an Ethereum explorer to verify the call.
Reject any claim link or contract sent in an unsolicited direct message.
What proves that the withdrawal finished?
The Ethereum claim receipt must succeed, and the expected native ETH or ERC-20 balance must reach the recipient. Save the Sui source digest, bridge sequence or message identifier, and Ethereum claim hash together.
A “claimable” status is not completion; it is permission to perform the final transaction.
What if the $5 million outbound limit is reached?
The current interface states a rolling $5 million limit from Sui to Ethereum. A message can wait as hourly records age out of the trailing 24-hour window. Retrying creates a new withdrawal rather than speeding up the original.
Record the limiter status and wait for capacity or verified official guidance.
What information should be sent to support?
Provide the Sui transaction digest, source address, Ethereum recipient, coin type, amount, sequence or message ID, current status, limiter data, and any failed Ethereum claim hash. Public identifiers are sufficient; no legitimate support process needs wallet secrets.
Outbound claim workflow assessed July 16, 2026. Verify live contract and limiter state.
Top comments (0)