Transaction Manager Service

The Transaction manger is our internal service responsible for tracking and reporting the status of all user transactions across supported chains in real time.

🧠 Why It Matters

In Web3, tracking a transaction is notoriously unreliable and inconsistent across chains. Users often have to:

  • Manually open block explorers

  • Refresh UIs

  • Wait without knowing if something failed

The Transaction manager solves this by offering a reliable, chain-agnostic tracking layer that:

  • Registers transactions as they are sent

  • Watches them in real time

  • Pushes updates to the frontend (e.g. Success, Failed , Rejected )

⚙️️ How It Works

  1. Transaction is registered via our internal API, with chainId, hash, context.

  2. The manager uses chain-specific watchers (from Config Provider) to monitor status.

  3. It detects confirmation, failure, or timeout via polling or websockets.

  4. Pushes updates to frontend & database via events.

🚀 Scales Easily

  • Adding a new chain = config update, no code changes

  • Supports parallel tracking of multiple transactions

  • Designed to support both frontend notifications and backend auditing

  • Efficient: only polls when needed, prefers socket where available

PreviousBalance ProviderNextBridge-Dex Module

Last updated