thor swap routes: when to use each path

THORSwap routes a trade through a supported cross-chain protocol, a same-chain DEX aggregator or a price-optimised streaming swap, depending on the assets and available routes. Its documentation lists THORChain, Maya Protocol, NEAR Intents and Chainflip as providers, while Ethereum and other EVM token swaps can draw on local DEX liquidity. A route that appears for one asset pair may not appear for another.

For a thor swap, start with the asset pair and the quote: check the estimated output, fees and execution settings before approving. THORSwap’s own docs describe the interface as a route across these protocols, so the selected path matters as much as the token names. In this account, thor swap refers to that routing choice, rather than to a single swap mechanism.

Which thor swap route works across chains?

For moving between supported assets on different networks, use a cross-chain route when the quote shows the destination asset you want. THORChain and Maya Protocol use liquidity pools and process swaps across chains; THORSwap also lists Chainflip and NEAR Intents among its providers. Each route depends on its own supported assets and liquidity, so compare the quoted output and expected completion time shown for the trade.

These routes can deliver native assets without relying on a wrapped version, according to THORSwap’s documentation. That does not make all routes identical: each protocol has its own execution process, and the interface may offer only one route for a particular pair.

When should you use a DEX aggregator route?

Use a same-chain aggregator route when both tokens are on a supported smart-contract network and the swap can draw on local DEX pools. THORSwap documents Ethereum aggregation across liquidity sources including Uniswap, SushiSwap, 1inch and 0x; its BNB Smart Chain documentation names PancakeSwap. The aggregator combines available liquidity to quote a token swap, and can route the resulting asset onward for a cross-chain trade.

This path is useful for long-tail tokens that may not have a direct pool on a cross-chain protocol. It can add a swap step, however, so inspect the total estimated output and network fees. A longer route is not automatically a better-priced one.

Should you choose streaming or a faster route?

Choose streaming when the quote offers it and reducing price impact matters more than finishing quickly. THORSwap says THORChain and Maya Protocol divide the trade into smaller swaps over time, then send one combined output; its docs describe this as a way to seek better average execution on larger trades. A regular swap is the simpler choice when speed matters more.

• Cross-chain protocol: choose it for supported assets on separate networks.
• Same-chain aggregator: choose it for tokens with local DEX liquidity.
• Streaming swap: consider it when the quote offers a price-optimised option.
• Regular swap: consider it when timing outweighs the chance of lower price impact.

Before signing, confirm the destination asset and address, review the quoted minimum output and leave enough of the input-chain token for network fees. THORSwap’s available routes and quote details can change with the pair and liquidity. The next step is to compare the live quotes; the best route for a specific trade remains unconfirmed until those quotes are shown.