Bridged Tokens on Sui: Track Arrivals Through Balance Changes
Detect incoming bridged tokens on Sui programmatically by paging transactions for an address and crediting positive balanceChanges that match the full coin type.
The Tareom Editors4 min read

To detect bridged tokens arriving at a Sui address, query transactions involving that address and inspect each transaction’s balance changes. Those changes identify the owner, full coin type and signed amount, so your app can record a matching positive amount as an arrival.
Say an address already holds 10 tokens. It receives 5 more through Suibridge, then spends 5 before your next balance poll. The total still reads 10: polling alone misses the deposit. Reading each transaction’s balance changes shows the incoming 5 and the later outgoing 5 separately.
What should you query for each address?
Start with the recipient address and the exact Move coin types your app accepts. A coin type is the token’s fully qualified on-chain identifier. If you accept ETH issued through Suibridge, configure that token’s full coin type, rather than relying on its ETH symbol.
With a provider that still serves Sui JSON-RPC, use suix_queryTransactionBlocks with a ToAddress filter for the recipient. Request transaction effects with balance changes, and follow the pagination cursor returned by each page. Keep the filter, ordering and cursor together so a restart continues the same query.
For a new production integration, check your provider’s supported interface: Sui Foundation mainnet full nodes have disabled JSON-RPC. With Sui GraphQL RPC, query transactions using an address filter and cursor pagination, then select each transaction’s effects and balance changes. GraphQL uses its own filter and cursor fields; the matching rule stays the same.
How do you turn balance changes into arrival records?
For each transaction, keep a balance change only when its owner is the recipient address, its full coin type matches an accepted type, and its amount is positive. The amount is signed: positive means the address received value, while negative means it spent value. Preserve the exact integer amount; convert it for display only when you know the token’s decimals.
Imagine the first page returns a transaction with a positive change for the configured coin type and recipient. Store an arrival containing the transaction digest, coin type and amount. Then process the next transaction and page. Save the new cursor only after every record in that page has been handled.
Use the transaction digest as an idempotency key, backed by a unique constraint in your storage. If the process fails after saving a record but before saving the page cursor, it can replay that page; the digest prevents the same transaction from crediting twice. If the RPC call fails or its data is behind, resume from the stored cursor when service returns. Do not reset to the beginning or advance past an unprocessed page.
A ticker is not a safe match: two bridges can issue different coins that both display as ETH. Matching the full coin type ties credit to the asset you meant to accept. Suibridge uses a lock-and-mint process, and Suibridge’s Ethereum and Sui costs covers the costs involved if you are assessing the wider deposit flow.
What must be confirmed before you credit?
Credit only after the transaction has finalized successfully and its effects show the expected positive change. A transaction digest identifies a transaction, but does not by itself prove that execution succeeded. Check the transaction status as well as the balance change.
Your arrival record depends on four pieces being in place: the right recipient, an exact accepted coin type, a successful transaction and a durable digest record. You can see the pipeline is ready when it can process a page, save its matching arrivals once, and resume at the next cursor after a restart. Keep the last cursor with the address and filter it belongs to.
Related
How do I find the full coin type of a bridged token on Sui?
Read the coin type from a verified transaction’s balance change or the token’s trusted metadata source, then configure the complete Move type string. Verify the identifier against the asset your app intends to accept; a familiar symbol alone is not enough.
How quickly is a Sui transaction final?
A transaction is final when its effects are certified by validator acknowledgements or it appears in a certified checkpoint. For deposit crediting, verify successful execution and the expected balance change; a transaction can be final even when it aborted.
Can a Sui arrival be linked back to its Ethereum deposit?
The Sui transaction digest identifies the Sui-side transaction, not the Ethereum deposit. To connect the two, use a bridge message or claim record that links both sides, if the bridge exposes one, and store that reference alongside the Sui digest.