Skip to the article
Blockheight

Crypto markets, protocols, policy

How to Estimate a Cross-Chain Swap Output

A cross-chain swap estimate starts with the route’s market price, then subtracts pool, protocol and transfer costs; compare net output and slippage limits before sending.

The Blockheight Editors··3 min read

How to Estimate a Cross-Chain Swap Output

Estimate a cross-chain swap by checking the destination amount for your exact input, then accounting for every route leg, fee and price-protection limit. The amount you receive can differ from a simple market-price conversion because the route trades through liquidity pools and sends a separate transaction on the destination chain.

What determines a cross-chain swap estimate?

The route, pool liquidity and fees determine the quoted output. A direct pool swap has one trading leg; a route through an intermediate asset has more than one, and each leg’s price and liquidity affect the final amount. For example, Chainflip’s protocol documentation describes a BTC-to-ETH route through USDC as two sequential pool swaps.

Start with the quote’s estimated destination amount, not just its displayed exchange rate. Check whether the quote includes a broker fee, protocol fee, pool fees and an estimated destination-chain broadcast fee; some costs are deducted from the input, while others reduce the final output. The source-chain transaction fee you pay to send the deposit may be separate.

For the wallet choices behind that service, read about Chainflip’s four wallet swap routes. The route helps explain why two quotes for the same asset pair can show different net amounts: they may use different pools, fee settings or intermediaries.

How do you compare quotes fairly?

Compare the amount that should arrive, using the same input size, destination asset and recipient chain. A headline rate can omit costs or describe only the pool trade, so use the estimated output after fees when deciding which quote is better.

  • Confirm the input amount and whether the quote treats it as gross or net of any source-side fee.
  • Read the route and count its trading legs; more legs mean more pool pricing and fees to account for.
  • Check the fee breakdown, including broker charges and destination-chain transfer costs.
  • Compare the quote time and any expiry or execution window, since pool prices can move before the swap executes.

For a rough check, convert the input at the quoted route price, then subtract the listed fees in the assets and stages where they apply. Use the provider’s net output as the practical figure; a hand calculation may miss fee conversions, rounding or transfer costs.

What can make the final output differ?

Market movement and available liquidity can change the execution price between the quote and the completed swap. A larger trade can also move the price more within a pool than a smaller one, so a quote for a test amount may not predict the output for a much larger deposit.

Price protection sets conditions for execution rather than guaranteeing the quoted amount. Chainflip’s documentation distinguishes a minimum accepted price, which compares execution with the quote, from live-price protection, which compares it with an oracle price; either can delay or prevent a swap if its limit is not met during the allowed retry period. Check the refund address and retry period before sending if the interface offers these settings.

Which number should you use?

Use the net destination amount as your estimate, and compare it only with quotes for the same assets, amount and destination. Treat it as an estimate until the swap executes and the destination-chain transfer completes; the provider’s status updates can show whether the deposit, swap or payout is still pending. The final amount, execution time and any refund remain unconfirmed until those steps finish.

Related stories