# Bridge Transfer Tracker

> Where is my bridged money? Finds the bridge deposit in a transaction and checks if it arrived. Paste the source-chain transaction of a bridge transfer. The tracker reads its logs from the chain, recognises Circle CCTP (v1 and v2), Across, the canonical OP Stack bridges and Arbitrum inbox deposits, decodes token, amount, sender, recipient and destination, and asks the protocol's own status service (Circle Iris attestation, Across deposit status) whether it was delivered.

Part of usefulweb.site (https://usefulweb.site/). Results are deterministic calculations from the inputs and the listed assumptions; the API returns exactly what the web page shows.

## Use it
- Human interface: https://bridgetransfertracker.usefulweb.site/ (interactive tool at https://bridgetransfertracker.usefulweb.site/tool)
- JSON API: POST https://bridgetransfertracker.usefulweb.site/api/v1/calculate with a JSON object of inputs (schema: https://bridgetransfertracker.usefulweb.site/api/v1/tool)
- OpenAPI: https://bridgetransfertracker.usefulweb.site/openapi.json
- MCP (Streamable HTTP): https://bridgetransfertracker.usefulweb.site/mcp - tool `bridge_transfer_tracker`

## Inputs
- chain (select): Source chain (where you sent from)
- txHash (text): Source transaction hash
- logs (textarea): Or: receipt logs as JSON (offline) - The "logs" array from eth_getTransactionReceipt.

## Method
- Logs come from eth_getTransactionReceipt (or your pasted JSON). Event topics are computed with Keccak-256 from the protocols' published event signatures (Circle CCTP TokenMessenger v1/v2, Across SpokePool, OP Stack L1StandardBridge/OptimismPortal, Arbitrum Inbox).
- Amounts: USDC (CCTP) has 6 decimals; other tokens are read with decimals() on the source chain when online.
- Status: CCTP → Circle Iris attestation API (v1/v2); Across → Across deposit-status API; canonical rollup deposits are relayed by the rollup protocol and are described, not polled.
- Pasted logs are decoded without any network call (status "offline").