Cross-chain swaps depend on the destination wallet

A cross-chain swap sends an asset from one blockchain and pays out another asset on a destination chain, so the receiving address must be valid for that chain and asset. In THORChain’s documented BTC-to-ETH route, the network swaps through RUNE internally and sends native ETH to the destination address.

Checking the receiving wallet before sending can prevent a completed swap from paying an address you cannot use.

What does a cross-chain swap send to the destination wallet?

It sends the selected output asset to the address supplied for the destination chain. THORChain’s swap documentation describes a BTC-to-ETH swap as two pool trades, BTC to RUNE and RUNE to ETH, followed by an outbound ETH transaction from a network vault. RUNE is part of the route; the user does not need to receive or manage it.

This is a protocol-mediated swap, not a transfer of BTC onto Ethereum as a wrapped token. The output is ETH on Ethereum when that is the asset selected. Other interfaces and routes can support different chains or tokens, so the asset label and destination network shown at confirmation matter. For a fuller account of the BTC-to-ETH route, see thor swap.

How do you check that the receiving address is right?

Confirm the destination chain, asset and address together. An address that looks familiar may still be for another network, and a wallet that displays several assets may not support every asset or chain in the same way. For an exchange deposit, check its instructions for the exact network and whether a memo or tag is required; a correct-looking address alone may not satisfy the deposit requirements.

Before signing the source transaction, review these details in the swap interface and in the receiving wallet or service:

• The output asset and destination network match what you intend to receive.
• The address belongs to a wallet or deposit account you control on that network.
• Any required memo or tag is present and matches the receiving service’s instructions.
• The quoted output accounts for network fees, liquidity fees and price slippage.

THORChain’s user guide also tells swappers to review the amount, route, fees and slippage before confirming. The destination address is typically included in the swap instruction, so treat it as part of the transaction details, not a later withdrawal choice.

What happens if the destination is wrong?

A swap can complete on the source and protocol side while the payout goes to an unintended or unusable destination. Because the receiving transaction is made on another chain, the source wallet generally cannot reverse it after broadcast. A recipient address on an unsupported network, or one controlled by a service that does not credit the specific asset, may leave recovery dependent on whoever controls that address.

If the interface lets you set a refund address, check that separately: it is for a failed swap refund and does not replace the destination address for a successful payout. If an address or network is uncertain, pause before sending and verify it with the wallet or exchange that will receive the funds. The practical rule is simple: confirm the exact output asset and its receiving address before authorizing the input transaction.