Developers
Status & errors
How to track swaps safely and what to do when things fail.
Status lifecycle (conceptual)
You can model swaps as:
- created
- pending
- executing
- finalizing
- finalized (success) / failed (terminal)
Retry guidance
- Retry transient network errors with exponential backoff
- Treat “pending” as normal for cross-chain flows
- Only mark success when the swap is finalized
User messaging
Prefer messages like:
- “Preparing swap…”
- “Executing on destination chain…”
- “Finalizing…”
- “Done”
Avoid exposing internal component names or infra details in user-facing errors.