Check the Destination Before You Swap from a Wallet
Check the receiving chain, token and address before you approve a wallet swap; each field controls where the output can arrive and whether you can use it.
The Aeterna Sol Editors
A cross-chain wallet swap has two chain choices: a source and a destination. The destination determines where the output is sent, so matching the token name alone is not enough.
A token can exist on several networks, and an asset with the same ticker may be a different token contract on each one. The network and the receiving address need to work together for the result to be usable.
What should you check on the destination chain?
Check the destination network, the token you expect to receive and the address that will receive it. These details describe where the swap is meant to end, rather than just what leaves your wallet.
Start with the network name shown in the swap details. If the output is supposed to arrive on a particular chain, confirm that the destination field names that chain; a familiar token ticker does not confirm the network.
Then compare the output asset with what you intend to hold. Look for the full token name and, when the interface provides it, the token contract or other identifying details. A ticker can be shared by unrelated assets, so it is a weak check on its own.
Finally, check the receiving address. It may be your connected wallet address, or the interface may ask you to enter one. Confirm that it is the address you control and that it supports the destination network. For a pending transfer, use the guide to compare the acrossbridge transfer type that fits your route.
Why do the network and token need to match?
A wallet address is used to receive assets, but the chain determines which ledger records the transfer. A destination address can look familiar while the network selection is still wrong for your intended use.
Bridging and swapping can also be separate operations. A bridge moves value between networks; a swap changes one asset for another. Some routes combine both steps, while others do only one, so read the route description and output details instead of assuming “swap” means the same process everywhere.
The destination token may be a network-specific version of an asset. That can be useful when an app accepts that version on the selected chain, but it can cause friction if you expected a different network or token representation. Check that the receiving app or wallet can display and use the asset you are choosing.
Fees and timing can vary with the route and network conditions. The quoted output is an estimate shown before approval, and the amount received can depend on execution details. Compare the displayed minimum received, if provided, with the amount you are willing to accept.
How do you verify a wallet swap before approval?
Read the transaction details in order, from what leaves your wallet to what should arrive. Before you approve, use this sequence:
- Confirm the source network and the asset being spent.
- Confirm the destination network and the output asset, including any token details shown.
- Check the receiving address and make sure it is yours or otherwise intended.
- Review the estimated output, minimum received and fees, then compare them with your expectations.
If any field is missing, ambiguous or different from what you selected, stop before signing and inspect the route again. A wallet signature authorizes the transaction described in the wallet prompt; it does not guarantee that an incorrectly chosen destination will be recoverable.
What should you do if a transfer is already pending?
First, check the transaction status and destination details in the wallet or service that initiated it. A pending status means the operation has not finished, but it does not by itself show that the destination is correct or that you can change it.
Do not submit a second transaction just because the first one is taking time. Check whether the route has a documented status or recovery step, and use the transaction identifier if the service provides one. The right action depends on where the transfer is in its process; an already submitted transaction may not be editable.
When choosing a route in advance, prefer the option that delivers the asset on the network where you plan to use it. That usually reduces extra transfers and makes the destination easier to verify. For an Acrossbridge transfer, the useful comparison is the route and transfer type that match the state of your pending transaction.