Thor swap: choose native output for the chain you plan to use

Choose native output when you want the asset on its home chain; choose wrapped output only when you need a representation on another chain. In a thor swap, that choice decides what arrives in your wallet and where you can use it. A native asset is the chain’s own coin or token; a wrapped asset represents another asset on a different network, with its value depending on the arrangement that backs it.

That difference matters after the swap: the same asset name can refer to tokens on different chains, and a wallet or app may accept one version but not another. When you compare the options shown for a thor swap, check the destination network and the exact asset label. The linked reference to thor swap belongs in the same practical question: what do you need to do with the funds once they arrive?

What does native output mean in a thor swap?

Native output means the asset is delivered on the blockchain where that asset originates. If you swap into BTC, for example, native BTC arrives on Bitcoin; if you swap into ETH, native ETH arrives on Ethereum. You can then use it with wallets and services that support that chain, without first moving a wrapped representation back to its home network.

This is usually the simpler choice if your goal is to hold the asset or pay with it on its own chain. It also avoids taking on the extra token or bridge dependency associated with a wrapped version. The trade-off is that you need a destination address for the right network, and moving the asset later may require that network’s fees.

When should you choose wrapped output?

Choose wrapped output when the destination app or network needs that specific representation. A wrapped token can make an asset available in an ecosystem where its native form does not exist, but it is not interchangeable with native coins just because the ticker or market price looks similar. Support depends on the token contract, network and wallet.

Before confirming, check these details:

1. Confirm the destination network and address match the output you selected.
2. Check that your wallet or intended app supports that exact token version.
3. Review the quoted output and fees, including any cost to move or redeem the wrapped asset later.

How do you decide between native and wrapped?

Start with the next thing you plan to do. If you want to hold or spend the asset on its home chain, native output is generally the cleaner fit. If you need to use a supported app on another network, wrapped output may be necessary; confirm that app accepts the exact version you will receive.

In short, choose by destination and use, not by the word “wrapped” or a familiar ticker. For most readers who simply want the asset itself, native is the straightforward default. A wrapped option makes sense when its extra reach solves a specific compatibility need.