How to use thor swap from your own wallet

A thor swap from your own wallet starts by choosing the asset to send, the asset to receive and the wallet address that should receive it. Your wallet signs the transaction on the source chain; the swap route processes the exchange and sends the destination asset to the receiving address. The service does not need your seed phrase to do this.

How does a thor swap work from a wallet?

First, connect a wallet that holds the asset you want to send. A wallet connection lets the service read the address and prepare a transaction; it does not itself move funds. For a cross-chain swap, you may also need a wallet address on the destination chain. Some services let you connect both wallets, while others ask you to enter the receiving address.

Next, select the source network and asset, then the destination network and asset. These choices identify where the funds leave and what should arrive. Check the network as well as the token name: similar names can refer to different assets on different chains. If the job is to move value across chains and exchange it in the same process, thor swap offers a cross-chain bridge and swap service in a single flow.

Enter an amount and inspect the quote before signing. The quote estimates the output after the route’s exchange rate and costs. It can change before execution, especially when the market moves or the trade is large compared with available liquidity. The wallet then prepares the source-chain transaction. Depending on the asset, that can mean sending a native coin or approving a token contract before sending the token.

What should I check before signing a cross-chain swap?

Read the transaction details in your wallet and compare them with the swap you set up. A token approval gives a contract permission to use a specified token amount; it is separate from the swap itself. On some networks, the wallet may ask for this approval first and the deposit transaction second. A native coin does not use a token approval, but still needs a network fee.

• Confirm the source network, asset and amount.
• Check the destination network, asset and receiving address.
• Leave enough of the source chain’s native coin to pay transaction fees.
• Review the quoted output and any minimum amount shown before signing.

For a first transaction to an address you have not used before, check the address carefully and consider sending a smaller amount. A transaction on a public blockchain is generally difficult or impossible to reverse once confirmed. Never enter a seed phrase into a swap page or approve a wallet request that does not match the action you chose.

What happens after the wallet sends the funds?

The source-chain transaction must first be broadcast and confirmed. The swap route then detects the deposit, performs the exchange and sends the output on the destination chain. Think of the route as a courier carrying an instruction between two separate ledgers: the source wallet’s confirmation does not mean the destination transfer has already landed.

Keep the transaction record or hash and check the service’s status information if the output is delayed. Cross-chain swaps involve activity on more than one network, so the source transfer and destination delivery can have different confirmation times. If the source transaction fails, the wallet or service may show that status; if it confirms but the destination transfer is still pending, use the swap’s tracking details before trying again. Sending a second deposit can create a second swap.

The practical rule is to treat the wallet signature as authorization for a specific transaction, not as a general login. Choose the chains and receiving address first, check the quote and fees, then approve only the wallet prompts that match those choices. That sequence makes it easier to use thor swap while keeping custody of the wallet’s keys.