When Is a Crypto Bridge Transfer Complete?

A crypto bridge transfer is complete for its recipient when the destination chain records the specified assets at the intended address. A successful source-chain transaction starts the process; it does not by itself prove delivery.

Most bridges move value in stages because two blockchains cannot update one shared ledger atomically. A bridge may lock or burn tokens on the source chain, verify a message about that transaction, then mint or release assets on the destination chain.

What does a bridge transfer status mean?

A status describes one step in the route, and the wording depends on the bridge. Wormhole’s Wrapped Token Transfers documentation describes a source transaction, Guardian-signed VAA, and destination-chain redemption; Across describes an origin deposit, destination fill, and later settlement.

Those stages answer different questions: was the deposit submitted, was its message verified, and did the recipient receive the output? For example, Across marks a transfer “filled” when a relayer delivers assets on the destination chain; its later settlement reimburses that relayer and does not mean the user is still waiting for delivery.

How can I tell if the funds arrived?

Check the destination-chain transaction and the recipient address, then confirm the expected token and amount in that chain’s records. Wormhole says a VAA must be submitted to its destination token bridge contract before tokens are released or minted; Across says its `FilledRelay` event or status endpoint can show when a deposit has been filled.

A wallet display can lag or hide a token, so use the transaction record to distinguish a display issue from an uncompleted transfer. Also check whether the route requires a separate destination action or native gas to perform it; this account of ParaSwap and destination gas explains why an asset arriving without gas can leave a user unable to take the next step.

What should I do if the transfer is still pending?

Use the bridge’s own transaction tracker and compare its status with the source and destination records. If a message has been verified but no destination transaction appears, the route may still require a relayer or a user-submitted redemption; Wormhole documents both automatic and manual completion.

• Save the source transaction hash and check that it succeeded.
• Confirm the destination network and recipient address match the transfer.
• Look for a destination transaction that releases or mints the expected token.
• Check the bridge’s status for a pending fill, expiration, or required redemption.

Across says an unfilled deposit can expire and become eligible for a refund after its fill deadline. The next step is to follow the route’s tracker or redemption instructions; until the destination record shows delivery, the final outcome remains unconfirmed.