Treasury teams need two transactions to confirm a cross-chain transfer

A cross-chain treasury transfer is complete when the source transaction is final and the destination chain has executed the transfer into the intended account. A “submitted” or “in progress” status only confirms an earlier step, so treasury teams should verify both chains before reconciling the movement.

What should I check on the source chain?

Start with the transaction hash and confirm that the transaction succeeded on the correct source network. Check that the expected treasury wallet or contract sent the amount, and that the bridge or messaging contract emitted the transfer event.

Then check the chain’s finality status. A transaction visible in a block can still be vulnerable to a reorganization before it is final; Wormhole’s documentation, for example, describes finality as a chain-specific threshold before Guardians attest to a message. The required wait depends on the chain and the bridge’s configured security model.

How do I track the bridge message?

Use the bridge’s tracker or message identifier to follow the transfer after the source transaction. Depending on the system, the message may need to be observed, attested or signed, then relayed to the destination; an attestation proves that a message was validated, but does not by itself prove that it was executed.

Cross-chain systems can coordinate more than token movements: a fuller account of how omnichain messages coordinate activity across networks explains that broader model. For a treasury transfer, use the bridge’s own message record to match the source transaction to its destination attempt.

What proves the destination transfer completed?

Find the destination transaction hash and check it on the destination chain’s explorer. The transaction must succeed, and its event logs or state changes must show the intended action: for example, tokens released from a contract, minted to the receiving address or credited to a treasury vault.

Compare the destination network, recipient address, asset and received amount with the approved transfer. Account for bridge fees or a different token representation where applicable. If the bridge reports delivery but the destination transaction failed, the transfer is not complete; check the bridge’s documented retry or recovery process.

How should a treasury record the transfer?

Keep evidence from each stage so another reviewer can reproduce the check. A useful record includes:

• Source network, transaction hash, sender and finality status.
• Bridge message ID or attestation reference, if the bridge provides one.
• Destination network, transaction hash, execution status and recipient.
• Asset and amount sent, fees, and amount credited.

Reconcile the destination credit against the treasury ledger only after the destination transaction succeeds and the credited balance matches the expected net amount. If a transfer remains pending, record it as in transit and investigate which stage has stalled rather than treating a source-chain debit as proof of receipt.

The next step after verification is to retain both transaction hashes and the bridge record with the treasury’s transfer approval, then close the ledger entry against the destination balance.