Ethereum-to-Sui bridge transfer states: an evidence model
Represent Ethereum-to-Sui bridge transfer states from receipts, bridge records and Sui execution; keep RPC freshness separate so recovery stays clear.
The Crypto Front Page Desk4 min read

Represent Ethereum-to-Sui bridge transfers as a sequence of evidence-backed stages, with a separate freshness indicator for what your app has most recently observed. Settlement crosses independent systems: an Ethereum receipt, bridge records and Sui execution describe different steps, so one generic “pending” label hides useful progress.
Move from approval to destination execution
For an ERC-20 transfer, start with the token approval: the user authorizes the bridge contract to use the chosen amount. Approval success enables the deposit, but does not mean the transfer has started. The user still needs to sign the deposit transaction.
After signing, show “Source transaction pending” while the Ethereum transaction awaits a receipt. A successful receipt moves the transfer to “Source confirmed.” Keep “Confirmations remaining” separate until the receipt has the confirmation depth your app requires. Then look for matching bridge records and show “Bridge approved” when those records confirm processing. “Destination pending” means the matching Sui delivery has not yet completed.
Suibridge uses a lock-and-mint process for supported assets, so the source deposit and destination delivery belong to one transfer but occur on different chains. For the receiving side, see how to set up a Sui wallet for bridged tokens and find the coins. Suibridge’s destination context helps readers connect delivery to the wallet that should receive it.
Mark the transfer “Complete” only after successful Sui execution effects match the bridge transfer and show delivery to the intended address. Ethereum’s receipt confirms the source transaction; Sui’s execution effects confirm the destination transaction. The distinction gives users a clear account of what changed at each step.
Keep the transfer record and observation freshness separate
Persist enough identity to reconcile evidence across retries and devices: source and destination chains, sender and recipient addresses, asset, amount, transaction hashes, source event identity and bridge message key. Use those fields to match a bridge record to the deposit and a Sui delivery to the same transfer. A hash alone identifies one transaction, while the event identity and message key help connect the transfer across systems.
Store the transfer stage separately from observation freshness. The stage describes the latest verified lifecycle event. Freshness describes when your app last checked an RPC or authoritative bridge record, and whether that check succeeded. An RPC outage can make the display less current while the transfer continues processing elsewhere.
For instance, say a user approves an illustrative ERC-20 amount, signs a deposit, and the Ethereum receipt arrives. Your app advances from “Source transaction pending” to “Source confirmed,” then later to “Confirmations satisfied” and “Bridge approved” as matching evidence appears. If an RPC request then fails, keep the latest verified stage and show “Last checked” with its time plus a “Status may be delayed” indicator. After a successful refresh, update the observation time and stage only if new evidence supports it. The transfer record stays the same; confidence in the display changes because the evidence is newer.
When processing appears stalled, show the current stage and the time of the last observation. That gives the user a useful next step: wait or refresh, rather than treating a temporary data gap as a new transfer state.
Represent exceptions as explicit states with actions tied to the evidence. A rejected wallet signature leaves the deposit unsigned; offer “Try again.” A replaced Ethereum transaction should point to the replacement hash and resume receipt tracking there. A reverted source transaction should show “Source reverted” and explain that the deposit failed, with an action to review and retry. Keep the original hashes and event details in the transfer record so support and the user can trace what happened.
How should my app show bridge progress percentage?
Use named stages instead of a percentage: elapsed time gives an unreliable measure of progress when Ethereum confirmation, bridge processing and Sui execution take different amounts of time. Pair the stage with the relevant transaction or confirmation detail.
Should my app use bridge webhooks or polling?
Reconcile webhook notifications against authoritative chain records. Polling can refresh the same evidence when notifications are missed, while the persisted transfer identity lets both paths update one record without inventing a second transfer.
The model changes the display from a single spinner into a sequence users can understand: approval, source settlement, bridge processing and destination delivery. Watch the evidence for each transition and the age of your latest observation; together they show both where the transfer stands and how current that view is.