How to Check a Cross-Chain Swap Before Sending

Check the destination chain, asset, address, and expected amount before you approve a cross-chain swap. These checks catch the common mistakes that can leave funds on the wrong network or in an unexpected form.

Start by naming the asset you need at the end

Write down both the destination network and the exact asset you want there. “ETH” alone may be unclear: you might need native ETH on Ethereum, or an ETH version on another chain.

Tokens with the same name can be different assets on different networks. A wrapped token is a network-specific version of an asset, such as WBTC on Ethereum; it represents Bitcoin, but it is not native BTC on Bitcoin. If an app or person will receive the funds, check which version they accept.

A cross-chain bridge and swap service can move and swap assets across networks in one flow. For example, you could send BTC and receive ETH on Ethereum without arranging each cross-chain leg yourself. The route still needs to match the asset and network you actually plan to use.

Check the route before you approve it

A route shows how the service expects to turn your starting asset into the destination asset. Read its source network, destination network, and asset names together; a familiar ticker by itself does not confirm the right route.

If you are comparing transfer types, which thor swap route fits is a separate question from whether this particular destination is correct. A thor swap can simplify a cross-chain move, but you still need to verify what arrives and where.

Follow these steps before signing:

1. Set the destination first. Choose the network and asset required by your end use. If you are sending to an exchange or app, check its deposit instructions; it may accept only one network or token form.
2. Match the source and destination. Confirm the route begins with the asset you hold and ends with the asset you need. For example, BTC to ETH on Ethereum should not end in wrapped BTC or ETH on a different network.
3. Check the receiving address on that network. Copy it from the destination wallet or service, then compare the first and last characters. Some Ethereum-compatible networks use similar-looking addresses, so the address alone may not reveal which network is selected.
4. Look for a memo or tag requirement. A memo is extra text or a number that helps identify a deposit. Include it only when the receiving service requires one, and copy it exactly; a correct address may not be enough for an exchange deposit.
5. Read the estimated output and minimum. The estimate can change before completion as prices and liquidity move. Slippage means the difference between the expected and actual swap price; check the minimum output, which is the least the route says you should receive.

Understand what happens after you send

The swap usually has more than one stage: the source-chain transaction must be recorded, the cross-chain service processes the transfer, and the destination-chain transaction delivers the output. A confirmation means the source network has accepted a transaction; it does not always mean the destination delivery is complete.

Keep the source transaction record and wait for the destination transaction or balance to appear. If the source shows complete but the destination has not arrived, check the route’s stated status and the destination network before trying again. Sending a second swap can create a second transfer rather than fix the first.

For a quick example, say you want to pay an app that accepts native ETH on Ethereum. If the quote instead delivers an ETH token on a different chain, the amount may look right while the payment still fails. The decisive check is the app’s accepted network and asset, not just the ticker.

Pause when the destination has special rules

Take extra care when sending to an exchange, payment service, or smart contract. A smart contract is a program on a blockchain; it may accept only specified tokens or networks, and some deposits require a memo or tag. Verify the recipient’s current instructions before sending, especially when a transfer cannot be reversed by the recipient.

If you cannot confirm the network, asset form, or memo requirement, do not approve yet. The answer changes when the destination accepts several networks or specifically requires a wrapped asset: follow its instructions, even if that means choosing a different route or transfer type.