A bridge transfer has separate source and destination transaction hashes because each chain records a different transaction. The hashes identify the two on-chain actions that the bridge links into one transfer.
What do two hashes represent in a bridge transfer?
Take a USDC transfer through lifi bridge using Across. The source transaction deposits USDC on the sending chain; call its hash A. After the bridge’s settlement process, a relayer submits a fill transaction on the destination chain; call that hash B. Each transaction is executed and recorded independently, so hash A belongs to the source chain’s history and hash B to the destination chain’s.
The status response gives each leg its own field. On a lifi bridge, those fields are sending.txHash and receiving.txHash, so tracking a lifi bridge transfer across chains is a concrete way to follow both records. The separate fields reflect separate transactions, not two names for one transaction.
Across relayers submit destination fill transactions. That step matters because the destination chain records the relayer’s transaction, even though the transfer is intended for your address. The source transaction and destination fill are connected by the bridge’s messaging or settlement mechanism; they are not one transaction spanning both chains.
How do you identify the beneficiary in the destination transaction?
Read the destination receipt’s logs to identify the address that received the bridged tokens. The receipt’s From field can name the relayer, since the relayer submitted the fill transaction; that field identifies the transaction sender, not necessarily the beneficiary.
For USDC, find the relevant ERC-20 Transfer event in the destination receipt. Its from and to fields record the token movement: the to address is the recipient of that transfer. Match the event to the destination token and amount for the bridge fill, since a receipt can contain multiple logs. This lets you distinguish the relayer that paid for and submitted the transaction from the address that received the tokens.
A route can also include approvals or swaps executed as separate transactions. An approval may happen before the source deposit, and a swap may take place on either chain. Each adds its own transaction hash, so a complete route can involve more than two hashes; the count depends on which steps require separate on-chain transactions.
What other identifiers can appear in a bridge route?
bridge message id vs transaction hash
A message ID identifies bridge-specific communication or settlement, while a transaction hash identifies one on-chain transaction. A message may relate to actions on both chains, but it is not a substitute for either chain’s transaction hash.
do internal transactions have their own hash
Internal calls appear within their enclosing transaction and share its transaction hash. They may show additional execution details, but they are not separate top-level transactions in the chain’s transaction history.
- Source and destination transactions have separate hashes because they occur on separate chains.
- The destination transaction’s sender may be a relayer; use the token’s Transfer logs to find the recipient.
- Approvals and swaps can add more transaction hashes to a route.