web3-news

3 Reasons Back-to-Back Cross-Chain Swaps Differ

Back-to-back cross-chain swaps can return different amounts because pool prices, market rates, and execution timing change between trades. A quote is an estimate based on conditions at that moment, not a promise that every later swap gets the same rate.

1. Each swap changes the available pool price

A liquidity pool is a shared supply of two assets used to make trades. When a swap takes some of one asset and adds the other, the pool balance changes, so its next exchange rate can change too.

Cross-chain services may route a trade through one or more pools or markets. For example, a service such as thor swap coordinates a move between chains and a swap between assets in one flow; each part can take time, and the eventual output depends on execution conditions.

Here is a calculation you can redo. Say a quote shows 1 BTC for 20 ETH. If a later quote is 1.5% worse, estimate the output as 20 × (1 − 0.015) = 19.7 ETH, before any separate costs. The gap may reflect a changed pool balance, a changed market price, or both.

2. Why does a pending swap get a different rate?

A cross-chain swap has several events: the source-chain transaction must be confirmed, the swap must execute, and the destination-chain transfer must be sent and confirmed. While it waits, other trades can move pool prices, and the wider market can move too.

“Slippage” means the difference between the quoted rate and the rate available when the trade executes. Chainlink’s educational material explains that pool depth and trades made while a transaction is waiting affect this difference. A large trade against a shallow pool usually has more price impact, meaning the trade itself moves the rate more.

Some systems split a large swap into smaller trades over time. THORChain Docs describe this approach as a way to reduce the effect of one large trade on pool prices, though the swap can take longer. That does not freeze the market rate during the wait.

A minimum-output limit sets the least you agree to receive. If execution would fall below that floor, a swap can fail or be partly refunded, depending on the service and route. Raising the limit may let the trade proceed at a worse rate, so check the new minimum before changing it.

3. What should you check after a delay or failure?

First, check the original transaction on its source chain. Confirm whether it is still waiting, completed, or failed; then check for a destination transfer or refund before submitting another swap. A pending status alone does not tell you whether the swap itself has executed.

If the source transaction completed but the swap failed, the cause may be a price limit, insufficient available liquidity, or a delay that made the quote stale. If the destination transfer is pending, its chain may still be confirming it. Save the transaction IDs and compare the quoted output with the final output once the route settles.

When comparing two quotes, use the same input amount and compare the estimated output and minimum output. A fresh quote can differ even seconds later, so treat the second result as a new decision. If you are using thor swap for the next attempt, check the current minimum you would accept before you submit.