You select the right wallet, choose the right token, and still watch the balance stay at zero on the other chain. That is where the common myth starts: a bridge transfer is just a wallet-to-wallet send with a longer confirmation. It is not. The Across Bridge route involves a source-chain transaction, a destination-chain fulfillment, and settlement between the parties behind the scenes.
The practical catch is that “sent” does not always mean “available.” A transaction can be confirmed on the source chain while the destination transfer is waiting on a relayer, a route check, or the required liquidity. Refreshing the wallet will not fix a wrong network, an unsupported token, or a recipient address copied from the wrong chain.
What to check before you bridge
Begin with the smallest sensible test amount. Confirm the source network, destination network, token, and recipient address separately; do not rely on a familiar token symbol alone. USDC on one network is not automatically the same asset as USDC on another. Read the quoted amount after fees, then leave enough native gas token on the source chain to approve and submit the transaction.
Before signing, compare the displayed destination amount with what you expect and inspect the transaction in your wallet. The safest route is to use the Across Bridge flow only after those details match. Save the source transaction hash. If the destination balance is delayed, use that hash to track the state rather than submitting a second transfer and accidentally paying twice.
What “safe” actually means
Safety here is mostly disciplined verification, not blind trust. A completed source transaction cannot usually be reversed, so a wrong chain or address is the expensive mistake. Keep the test small until the first transfer arrives, and remember that a fast destination credit does not remove the need for final settlement on the source chain.
The myth is useful only if it is replaced with a better model: bridging is a coordinated cross-chain transfer with several checkpoints. Check the route, sign once, keep the hash, and wait for the destination balance to appear before doing anything else.