Check the token before a cross-chain transfer

Check a token’s network and contract address against the bridge’s route before starting a cross-chain transfer. A ticker such as ABC is only a label: different tokens can use the same ticker, and the same asset can have different contract addresses on different networks. Confirm the exact asset the route accepts and what it delivers.

How do you verify a token’s identity?

Use the contract address, network and token name together. Find the address in the project’s official materials, then compare it with the token entry shown for the source network in the bridge interface; a matching name or ticker alone is not enough.

Check the destination side too. A bridge may deliver a wrapped representation or another token that tracks the source asset, rather than the same contract address. The destination token’s address and network tell you what will actually arrive in your wallet.

• Confirm the source network selected in your wallet and in the bridge.
• Compare the full token contract address, not just its shortened display.
• Check the destination network and the token the route says it will deliver.
• Review the amount after fees before signing the transaction.

How do you check whether a bridge route supports it?

Check that the bridge offers a route for that specific source token and destination network; support for a network does not mean every token on it can use every route. Routes can differ in fees, waiting steps and the asset delivered. For the Bitcoin-to-Ethereum timing comparison, see Acrossbridge Bitcoin-to-Ethereum route times.

Before approving, compare the quoted output with the asset you intend to receive. Some bridges lock tokens on one network and release tokens on another; others burn and mint representations. The mechanism affects what the destination asset is, so follow the route’s stated output rather than assuming the ticker will match.

What should you check before signing?

Read the wallet prompt and confirm the network, token, amount and destination details. Check whether the bridge requires a separate claim or follow-up transaction, and keep enough of the destination network’s native token for any later transaction fees.

If the address, network or expected output differs from the route details, stop and verify the token through the project’s official materials. Once submitted, a cross-chain transfer may not be reversible. The route’s current status and final delivery time remain unconfirmed until the bridge processes the transfer.