Skip to main content

Tracking Status

After a swap transaction is broadcast, you need to track its completion on the destination chain. Rubic SDK provides both a direct status method and a higher-level polling helper.

getStatusExtended

Fetches the current status of a cross-chain transaction in a single request.

Request parameters

When is srcTxHash required?
  • Decentralized providers (bridges, on-chain DEXes): both id and srcTxHash are required
  • Deposit-based providers (ChangeNOW, Exolix, etc.): only id is needed

Example

Response: StatusResponseInterface


Transaction statuses

Terminal statuses mean no further polling is needed.

waitForStatus

A built-in polling helper that calls getStatusExtended on an interval until a terminal status is reached.

Options

Example — basic usage

Example — with all options

Example — handling all outcomes

Example — deposit-based providers (no srcTxHash)


READY_TO_CLAIM — Arbitrum Bridge

When status === 'READY_TO_CLAIM', the swap used the Arbitrum Bridge and requires a manual on-chain claim on the destination chain. Use claim() to build the claim transaction: