Exact-output swaps need a fresh quote as pool state moves

An exact-output swap fixes the amount of tokens you receive and calculates how much input it should take, so its quote needs refreshing when pool state changes. A quote is an estimate from a snapshot of liquidity, not a reservation. Before the transaction executes, other swaps can change reserves or move liquidity across a concentrated-liquidity tick.

Why does an exact-output swap need a new quote?

An exact-output quote works backward from the requested amount. In a constant-product pool, the calculation inverts the pool’s swap formula and accounts for fees. In a concentrated-liquidity pool, it must account for the active liquidity and any tick crossings needed to deliver that output. For a multi-hop route, each pool’s required output becomes the preceding pool’s target, so a change at one hop can change the total input estimate.

That estimate can become stale while a user reviews or signs a transaction. A new quote recalculates the route against newer pool state and gives the trader a current estimate of the input required. For the separate question of when to trade or provide liquidity, see Byreal’s guide to choosing swaps and pools. The two decisions use different mechanics: a swap executes against pool liquidity, while providing liquidity adds assets to it.

What does the slippage limit protect?

An exact-output transaction sets a maximum input the swap may consume. The quote estimates the input, and the slippage setting allows that amount to move within a defined bound. If execution would require more than the maximum, the transaction fails instead of spending beyond the cap. The cap does not guarantee execution: a changed pool price can make the trade fail even when the requested output remains unchanged.

Refreshing the quote updates the estimate; it does not lock in the price. The on-chain swap instruction checks the pool state when the transaction executes. This is why the trader should review the maximum input as well as the quoted input before signing.

When is exact output the better choice?

Exact output fits a payment or settlement where the recipient must receive a specified token amount. Exact input is usually the simpler choice for a discretionary trade: it fixes the spend and lets the received amount vary within the transaction’s minimum-output bound. Exact-output support also depends on the pool and route, so the available paths may be narrower.

• Use exact output when the received amount is the requirement.
• Refresh the quote after a delay or a material change in the displayed route.
• Check the maximum input, not only the estimated input.
• If the new cap exceeds your budget, reduce the requested output or wait.

Repeated quotes are useful when they update the decision with fresher pool state. They cannot make a moving market fixed. For most swaps without a hard receipt amount, exact input offers a clearer control: set the spend, then accept only the output allowed by the transaction’s minimum threshold.