A token swap estimate is a quote, not a promise
A token swap estimate combines pool price, fees, route depth and slippage; checking those parts before signing shows what can change before on-chain settlement.
By The Coin Wire Editorial6 min read

A token swap estimate shows the expected output, route and costs before a transaction is signed, but it cannot guarantee the amount that will settle. The shift from reading a pool’s displayed price to inspecting a complete quote matters because the displayed price leaves out trade size, fees and changes while a transaction is pending. A useful estimate separates those parts so you can judge whether the quoted output is acceptable and set a minimum before authorizing the trade.
How does a token swap estimate work?
A swap estimate simulates a trade against available liquidity and reports the output the route would produce at that moment. In a liquidity pool, the price depends on the pool’s token balances and the pool’s pricing rule; a trade changes those balances, so a larger order can receive a worse average price than the rate shown for a small one. The quote is therefore an estimate for a particular input amount, route and time, rather than a standing offer.
Some swaps use one pool, while others route through multiple pools or intermediate tokens to find a better expected result. A split route can draw on several pools, but more steps may add fees and make the transaction harder to assess. For a fuller explanation of how trade types affect execution, see fermi swap. In either case, the quote should identify the assets being exchanged and the estimated output, not just a headline exchange rate.
Read the estimate as a set of components:
- Expected output: the amount the route predicts you will receive before settlement.
- Price impact: the effect your trade has on the pool price, distinct from later market movement.
- Route and pool fees: charges applied by the pools used along the path.
- Network cost: the fee for submitting and processing the transaction, usually paid in the chain’s native asset.
Interfaces do not always display these components in the same place. Check whether a quoted “received” amount is before or after protocol fees, and whether the network fee is included. A comparison is meaningful only when the input amount, route assumptions and fee treatment match.
What can change between the estimate and settlement?
The amount received can change because the transaction executes against conditions on-chain, which may differ from those used to generate the quote. Other trades can move pool balances before yours is processed. Network congestion can also delay inclusion, giving prices more time to move. The estimate is a snapshot; the transaction’s minimum-output setting is the bound that determines whether it can proceed at a worse rate.
Slippage tolerance sets how far execution may move from the quoted result before the transaction reverts. A tighter tolerance protects the output but can cause a failed transaction if the market moves slightly. A looser tolerance makes execution more likely to complete through movement, while allowing a lower output. It does not improve the quote or guarantee a better price.
Before signing, check the minimum amount you are willing to receive. Many swap transactions encode that amount as a minimum output; if the route cannot meet it, the swap should fail rather than settle below the limit. Confirm that the displayed minimum matches your own threshold, especially when the quote has changed after you entered the amount. A failed transaction may still incur a network fee because the chain processed the attempt.
Price impact and slippage are related in the final outcome but describe different things. Price impact comes from the trade’s size relative to available liquidity and is reflected in the current quote. Slippage is the permitted movement between quote and execution. A large trade in a shallow pool can have material price impact even with a low slippage setting; a small trade can face execution movement if the market changes while it waits.
How should you compare quotes before signing?
Compare the minimum output and total costs for the same input amount, rather than choosing the route with the most attractive displayed rate. A route with more pools may quote a higher output but incur additional fees or depend on several pools remaining usable. A direct route may be easier to inspect yet produce less output if its pool has less depth. The better choice for most readers is the route with a clear minimum received and a sensible total cost, not the one with the best isolated price figure.
For a practical check, pause at the confirmation screen and verify:
- The input token and amount, including the network on which the swap will execute.
- The estimated output, minimum output and slippage setting.
- The route, any displayed price impact, pool fees and network fee.
- Any token approval requested, including which token and spending allowance it covers.
Token approval is separate from the swap itself: it authorizes a contract to use a specified token amount, while the swap instruction performs the exchange. Read the approval prompt before signing, and check that the requested token and allowance make sense for the trade. If the quote changes materially while you review it, refresh the estimate and reassess the minimum instead of relying on the earlier numbers.
When is a quote good enough to use?
A quote is useful when you can explain its likely output, the lowest output you will accept and the costs required to attempt the trade. For a small, liquid swap, the difference between quoted and settled output may be modest, but the same displayed rate says little about a large order or a route through thin pools. If the minimum output is unacceptable or the fee is large relative to the trade, wait, reduce the size or compare another route.
The signals to watch are the gap between expected and minimum output, the route’s pool depth, the network fee and whether the quote remains stable when refreshed. Those figures reveal the trade-off: a better expected rate can come with more route complexity, while a tighter minimum protects the result at the cost of more failed attempts. Signing makes sense only when the minimum is an amount you are prepared to receive.