Thor swap types and the trade-offs treasury teams face

A treasury team moving crypto between chains can use a thor swap to exchange a supported asset directly for one on another network, without first routing through a centralised exchange. THORSwap presents routes across THORChain, Maya Protocol, Chainflip, NEAR Intents and other liquidity providers, so the available path depends on the assets and quote. For finance teams, the practical choice is whether to prioritise a faster settlement or give a larger swap more time to seek a better average price.

Choosing the route and execution pace changes both the expected proceeds and how long funds remain in transit.

Start by entering the source and destination assets, the amount, and the receiving wallet, then review the quoted output before signing the source-chain transaction. A thor swap can involve network costs on the sending and receiving chains, alongside the exchange fee and any price impact from the route. Keep a separate allowance for the sending wallet’s gas or network fee; committing the full balance can leave too little to move the funds.

What does a thor swap do for a treasury transfer?

A cross-chain swap takes the asset sent on one chain and delivers the selected asset to a wallet address on another. With a THORChain route, the network settles through its liquidity pools, using RUNE between pools when needed, rather than issuing a wrapped copy of the source asset. THORSwap also aggregates other providers, so a quote may use a different route; check the stated provider, output amount and fees rather than assuming every transfer uses THORChain.

This can reduce the operational steps compared with swapping on one venue, bridging, then trading again, but it does not make settlement instantaneous or remove market risk. Treasury records should capture the source transaction, destination address, route, quoted amount and final receipt, with the transfer approved under the organisation’s normal wallet controls.

Which thor swap type suits a treasury transfer?

For a routine payment with a deadline, a regular swap is the simpler choice: it executes as quickly as the networks and route allow. For a large trade relative to available pool depth, a streaming swap divides execution into smaller swaps over time and consolidates the result into one outbound transaction. That can reduce slippage, but it may take longer and leaves the order exposed to price movement while it runs.

• Regular swap: use when timing matters more than optimising the average execution price.
• Streaming swap: consider for larger trades when a potentially better average price justifies waiting.
• Aggregated route: compare the displayed provider and final output when the selected assets have several possible liquidity sources.

Streaming swaps are not a guaranteed price improvement, and THORSwap’s documentation says its current version cannot be cancelled once started. If the treasury cannot tolerate a changing market price or an open-ended settlement window, use a regular route or split the transfer under a policy that sets amounts and timing in advance.

What fees and checks should finance teams compare?

THORSwap’s published schedule lists a 0.5% exchange fee for swaps above $100; the quote can also include network fees and price impact, which vary with the route and conditions. Compare the net destination amount, not just the headline fee, and record the quote before approval because the final execution can differ as liquidity and network costs change. A thor swap should be sized against the receiving wallet’s required amount, with a buffer for fees where the quote allows for variation.

Before signing, independently verify the destination address and asset network, confirm the expected output and settlement route, and make sure the sending wallet holds enough native coin for its transaction fee. For most treasury transfers, a regular swap is the better default when delivery time is fixed; streaming is more appropriate when price impact is the larger concern and the team can wait.