Across Bridge: The “Completed” Mistake That Costs Funds

A bridge transfer worked only when the destination wallet can spend the received asset. A “completed” source-chain transaction proves that funds left; it does not prove that the destination-side claim, relay, or final execution happened.

The recurring disagreement is simple: one camp treats the source-chain success receipt as the finish line, while the other insists that only destination-chain settlement counts. The second view is right. The source receipt is necessary evidence, but it is not the operational result the sender paid for.

Did my across bridge transfer actually work?

It worked when three records agree: the source transaction is final, the relay or intent is filled, and the destination wallet shows a spendable balance in the expected token contract. Anything short of that is an in-progress transfer or an exception, not a completed bridge.

The mistake is trusting a green status without checking what that status measures. A wallet may report “confirmed” because the deposit transaction was mined. A bridge interface may report “filled” because a relayer accepted the route. Neither statement alone establishes that the asset arrived in the right wallet, on the right chain, in a form the recipient can use.

What is the definitive check for an Across bridge transfer?

The definitive check is a destination-chain explorer record showing the recipient address credited with the intended asset, followed by a balance check in a wallet that recognizes that token contract. For a route handled through across bridge, the other side is the destination network and recipient wallet—not merely a successful approval, deposit, or source-chain event.

Check in this order:

1. Confirm the source transaction has finality, not just a pending or replaced status.
2. Match the recipient address, destination chain, asset, and amount against the route you submitted.
3. Find the destination transaction and inspect its token-transfer logs.
4. Open the destination wallet on the correct network and verify the balance is available to send.
5. If the wallet balance is absent, add the verified token contract before deciding the transfer failed.

Why does a bridge say completed when the funds are missing?

Usually because “completed” describes one stage of a multi-stage process. The interface may mean the deposit was accepted, the relayer filled the order, or the settlement message was submitted. Those are useful milestones, but they are not interchangeable.

The part most guides skip is token identity. A destination balance can be real yet look missing because the wallet hides an unfamiliar contract, or because the sender expected a native asset while receiving its chain-specific representation. Compare contract address and decimals, not ticker alone.

How long should I wait before treating a bridge transfer as failed?

Wait only while you can identify forward movement. A source confirmation with no destination transaction is a reason to inspect the route and transaction details; it is not a reason to repeat the transfer. Sending again before resolving the first attempt is how a timing problem becomes an overfunding problem.

Escalate with the source transaction hash, destination chain, recipient address, expected token, and exact amount. Those five fields let support or a relayer trace the route; a screenshot of a green confirmation does not.

Across bridge FAQ: what do routine users still need to check?

Does the source transaction hash prove delivery?

No. It proves the source-side action. Delivery requires a destination-side record and a spendable balance.

Can I rely on my wallet’s displayed balance?

Only after confirming the correct network and token contract. Wallet displays are convenient; explorer logs are the audit trail.

Should I resend if the destination balance is delayed?

No. First trace the original route. A duplicate transfer is harder to unwind than a delayed one.