How to Track a lifi bridge Transaction: Confirm Receipt
You can confirm a lifi bridge transaction reached your address by looking up its source-chain hash in LI.FI Scan or the LI.FI API status endpoint, then opening the receiving transaction when the status is DONE with COMPLETED. For a LI.FI cross-chain bridge transfer, lifi bridge finds routes across supported bridges and decentralized exchanges; the selected bridge helps explain the status you see while tracking. The source hash connects both legs, although each chain records its own transaction hash.
- Result: A destination-chain receipt showing the token credited to your address.
- Have ready: The source transaction hash, both chains, and the receiving address.
How Do You Trace the Source Hash to the Receiving Transaction?
Trace the LI.FI transfer from your wallet’s source transaction through LI.FI Scan, then use the receiving hash to verify delivery. Start with the transaction that sent tokens into the bridge. A token approval is separate and its hash will not identify this transfer.
- Copy the source-chain hash from your wallet history and open it on the source explorer. You should see a successful receipt for the bridge transaction. If it reverted, investigate that source transaction before waiting for a destination receipt.
- Paste the hash into LI.FI Scan at scan.li.fi. The transfer record shows the bridge used, its status, and a destination transaction link when available. You can also search LI.FI Scan by wallet address to recover a missing hash. Say you initiated through Jumper Exchange and the route used Across or Stargate: read the underlying bridge on the transfer to identify which route is progressing.
- Read the PENDING substatus to find which side is waiting. WAIT_SOURCE_CONFIRMATIONS means the bridge needs more source-chain confirmations. Your source explorer may already show Success; wait for the bridge’s finality requirement. WAIT_DESTINATION_TRANSACTION means the destination transaction is outstanding. Keep following the source hash in LI.FI Scan while that bridge leg progresses. These states tell you whether to wait on source finality or watch for a receiving hash.
- In an app, request LI.FI API GET /v1/status with txHash set to the source hash. Adding fromChain speeds up lookup; bridge and toChain are optional. Poll with backoff until DONE or FAILED, reading the status and substatus each time. The possible statuses are NOT_FOUND, INVALID, PENDING, DONE, and FAILED. The response identifies the two legs as sending.txHash and, once recorded, receiving.txHash. LI.FI’s status documentation defines these fields.
- When the status is DONE with COMPLETED, open the receiving transaction on the destination explorer. Compare its chain, token transfer, and recipient with your intended address. The task is done when that receipt shows the token credited to your address. DONE with PARTIAL calls for inspecting what arrived; DONE with REFUNDED records a refund, not destination delivery.
Say the source explorer shows Success, but searching the same hash on the destination explorer finds nothing. That result can lead you to expect a missing transfer. The destination leg has its own hash; find it through LI.FI Scan or receiving.txHash in the API response.
Related
How long does a lifi bridge transfer take?
A LI.FI transfer’s duration depends on the chosen bridge and the source chain’s finality. A route using Across may progress at a different pace from one using Stargate. I would follow the live substatus instead of an elapsed-time guess because it identifies the outstanding leg: source confirmations or the destination transaction.
What to do when a lifi transaction shows NOT_FOUND?
NOT_FOUND means LI.FI has not matched the hash yet. It may appear shortly after broadcast or when the hash or source chain is wrong. Confirm the final broadcast transaction and its receipt on the source explorer, then retry with the correct fromChain. The API may also return HTTP 404 with code 1003 for an unknown hash. If a successful source receipt remains unmatched, preserve the hash and reconcile your wallet history before treating the transfer as failed.
After confirming the destination receipt, save its hash beside the source hash to keep a record of both legs.