If you have sent treasury funds across chains for the first time, confirm the transfer on both networks and check the receiving wallet’s token balance. A successful source transaction only proves that the funds left the first network. You still need to verify the destination transaction, recipient, token, and amount before recording the transfer as complete.
A completed transfer has a confirmed destination
A bridge transfer is complete when the destination network records delivery to the intended wallet. A transaction hash is the unique code you can use to find a transaction in a network explorer, a website that displays public blockchain records.
Some routes also swap tokens, so the token arriving may have a different name or amount from the one sent. Compare the destination token’s contract address, a blockchain identifier for that token, as well as its name. Across Protocol’s documentation describes tracking a deposit through states such as pending, filled, expired, or refunded; other routes can use different terms.
Check the transfer from source to destination
- Record the transfer details. Copy the source transaction hash and note the sending network, destination network, recipient wallet address, and expected output token. A wallet address is the public account identifier; check every character, especially if you copied it from a treasury record.
- Confirm the source transaction succeeded. Open the source network’s explorer and search the hash. Check that its status says successful, and note the input token and amount. If it is pending, the transfer has not yet been confirmed on the source network.
- Find the destination result. Check the bridge route’s status, then search the destination network for its transaction if one is shown. “Filled” generally means the route delivered funds; “pending” means it is still processing. If the route says filled, confirm the destination transaction succeeded too.
- Match the recipient, token, and amount. In the destination transaction, verify the recipient address and token contract against your records. Compare the received amount with the quoted output, allowing for any swap or route costs shown before sending. For example, a route from ETH on Ethereum to USDC on another network should end with USDC at the treasury’s wallet, not ETH in a staff member’s wallet.
- Resolve any mismatch before closing the record. A source success with no destination delivery can mean the route is still processing, not that funds vanished. Wait for the route’s stated deadline or status to update; if it expires or refunds, record that outcome and reconcile the returned funds before trying again.
Consider two cases: a source transaction still marked pending needs more time, while a source success followed by a destination fill can be reconciled once the recipient and token match. Ethereum.org explains that transaction finality means a block is settled enough to treat its transactions as very unlikely to change; the time required depends on the network. For a treasury, keep both transaction hashes and the final amount in the same record.
In practice, I would mark a transfer complete only after the destination record matches the treasury wallet and expected token. A bungee bridge aggregator can help find a route for moving or swapping tokens across chains; the bungee bridge service is one way to handle that route search. Keep the source and destination records together so another reviewer can verify the result.