Check the destination network, asset support, and full wallet address before you authorize a cross-chain swap. A wallet address is only a destination when it belongs to an account you can access on the network that will receive the funds.
Confirm the destination network and wallet type
First, confirm which network the destination wallet will receive on and whether it is a wallet you control or a deposit account at a service. A self-custody wallet may use one address across several compatible networks, while an exchange deposit can require a specific network and an extra memo or tag.
For example, an Ethereum-style address is typically 42 characters, starting with 0x; Ethereum.org’s account documentation explains that it represents a 20-byte address. Solana addresses use a different format: Solana’s account documentation describes them as 32-byte values shown as base58 strings. These formats help catch a mismatch, but they do not prove that a wallet can receive a particular asset.
- Network name shown by the receiving wallet or deposit page
- Asset name and, for tokens, the correct token on that network
- Whether the destination is self-custody or an exchange account
- Any required memo, tag, or other deposit reference
Match the address to the asset you plan to receive
Check that the destination can receive the specific asset on the selected network. A wallet may display the same Ethereum-style address on multiple networks, but the balances and token support are network-specific; seeing the same address does not mean the asset will appear in the network you intended.
how to choose an acrossbridge route determines which network your destination wallet needs to be ready for. An acrossbridge service moves or swaps assets across networks in one flow, so the destination network and asset are the details to verify before authorizing the transfer. If you are sending to an exchange, use its deposit instructions for that exact asset and network.
Consider two cases: a self-custody wallet whose owner controls the same account on both networks, and an exchange account that only credits deposits sent on its listed network. The first may accept the address on the destination network; the second can leave a deposit uncredited if you choose another network or omit a required reference.
Verify the destination before you authorize the transfer
Use these steps in order; each check catches a different kind of mistake before the source transaction is sent.
- Open the receiving wallet or deposit page. Find the receive instructions for the exact asset, then note the network and any required memo or tag. This gives you the destination details from the place that will actually receive the funds.
- Copy the full address from that source. Use the wallet’s copy function or the exchange’s deposit page instead of retyping or relying on an old address. A single wrong character can send funds to an account you do not control.
- Check the destination network in your transfer details. Make sure it matches the network specified by the receiving wallet or deposit page. With acrossbridge, confirm that the destination asset and network shown for the transfer match those instructions before proceeding.
- Check token support and account access. Confirm that your wallet can display and manage the incoming asset on that network. If the destination is a smart-contract wallet, check that it is available there; a familiar address alone does not guarantee the wallet is deployed or usable on every network.
- Review the final details before signing. Compare the full destination address, asset, network, and any required reference against your notes. If anything differs, stop and correct it before authorizing the source transaction.
Once the transfer has been sent, use the transaction record and the destination network’s block explorer to check for confirmation and receipt. A source-side success does not by itself prove that the destination wallet has credited the intended asset; check the destination network and token balance too.
Answers to common destination-check questions
Can I use the same address on two networks?
Sometimes. Ethereum-style wallets often show the same address on compatible networks because they use the same account key, but each network keeps its own balances and token activity. Confirm that the receiving wallet supports the asset on the destination network. For other address formats, use the address generated for that specific network.
How long should I wait before checking the destination?
Wait until the transfer’s status indicates that the destination step has completed, then check the destination network’s block explorer or wallet balance. Timing varies with network conditions and the transfer route, so a pending status alone does not mean the funds are lost. Use the transaction record to distinguish a delay from a completed receipt.
What if the address looks valid but the asset does not arrive?
Check the destination network, token, and transaction record first. An address can be correctly formatted yet belong to an unsupported wallet or a different network than the one you intended. For an exchange deposit, check whether its instructions required a memo or tag, and contact its support with the transaction details if the deposit remains uncredited.
Which destination should I choose for a quick transfer?
Choose the destination where you can actually access and use the received asset. A self-custody wallet suits someone who controls the account and can manage that asset on the destination network; an exchange deposit suits someone following that exchange’s exact deposit instructions. Convenience does not make a network mismatch safe.
The safest short path is to copy the receiving instructions, match the asset and network, and verify the full address before signing.