What a Chainflip Swap Estimate Actually Tells You

A Chainflip swap estimate is a forecast of the destination asset you may receive after the swap route and its costs are applied. It is not a promise of an exact payout: the price can move before the deposit is processed, and destination network costs can affect the amount sent.

What does the estimated output include?

Start with the input and output assets, then read the estimated output as the amount expected to reach the destination address. The protocol witnesses the source-chain deposit, processes the swap through liquidity pools, and broadcasts the resulting asset on the destination chain. If a route needs more than one pool, such as BTC through USDC into ETH, each leg is processed in sequence.

Liquidity providers compete to fill swaps in Chainflip’s just-in-time market. Think of the estimate as a snapshot of a market’s available offers: it describes what those offers imply now, while the final trade happens later. For the full sequence from deposit to payout, see this walkthrough of a first Chainflip swap. Its mechanics explain why the quote and the eventual payout can differ.

How do fees change the amount you receive?

Separate the trading price from the costs around it. Liquidity fees are charged as each pool in the route is used. The protocol may also take a network fee during swap processing. Then the network estimates the cost of broadcasting the output on the destination chain and deducts that cost from the final payout. You also pay the source-chain transaction fee when you send the deposit from your wallet.

These costs happen at different steps, so a single “rate” can hide them. Compare the estimated output for the same input amount and destination, and check whether the interface lists fees separately or folds them into the displayed amount. A route through two pools can have costs at both legs. A direct route avoids that extra leg, but the available liquidity and resulting price still matter.

What is the difference between output and slippage protection?

The estimated output is the expected result; slippage protection sets a boundary on whether the swap should proceed. Chainflip can enforce a minimum price or, for supported assets, a maximum deviation from an oracle price. If the swap cannot meet the configured limit within its retry window, the protocol can refund the deposit. Protection does not make the estimate certain: it defines a failure point instead of accepting a worse price.

Before sending funds, check these four details:

• Destination amount: Is this the amount expected after listed costs?
• Route: Does the swap pass through an intermediate asset or pool?
• Minimum or slippage limit: What price change will make the swap fail or be refunded?
• Addresses and networks: Do the destination asset, chain and wallet address match your intention?

Use a refreshed estimate immediately before you deposit, especially if the market has moved or you have changed the input amount. The useful comparison is not just the headline exchange rate; it is the expected destination amount, the costs that produce it, and the limit that determines whether execution can continue.