Why Treasury Swap Quotes Change Before Execution

A treasury swap quote changes before execution when the market state or the transaction assumptions used to calculate it change. The displayed output is an estimate from a particular route, input amount and observed state; it is not a reservation of liquidity or a binding execution price. For a treasury operator, the key distinction is between the quote’s estimate and the limits encoded in the transaction that gets signed.

A route can combine several liquidity pools, each with its own reserves and fee rules. A change in one pool can alter the route’s expected output, while a new route can replace it entirely. The recovery path after an unsuccessful attempt has its own mechanics; the fermi swap guide covers that process in detail.

What makes a treasury swap quote move?

A swap quote moves when the inputs to its route calculation change. For an automated market maker (AMM), the pool’s reserves determine the price available for a trade; the trade itself changes those reserves. If another transaction trades against the same pool before the treasury’s transaction, the remaining liquidity can produce a different output.

Quote services may also compare multiple pools or venues and select a route based on expected output after fees. A route can change when liquidity shifts, a pool becomes less favorable, or the service refreshes its view of available venues. A larger order can move the price more because it consumes more liquidity, and a multi-hop route compounds the effects of each pool’s fees and price impact.

Some components are not market prices. Network fees can change with congestion, and a cross-chain route may include bridge or relayer costs. A quote may also rely on a price feed or other reference data to value assets or screen routes. These inputs update on different schedules. A single displayed total can therefore move even when the headline token price appears steady.

Why can the execution price differ from the quote?

The execution price differs because the quote describes a proposed transaction against a particular view of state, while execution happens later against the state available when the transaction is processed. The gap between those moments leaves room for trades by other users, changing fees, delayed inclusion, and route-specific conditions.

For an on-chain swap, a minimum-output parameter sets the least amount the transaction will accept. If the route cannot deliver that amount when processed, the swap should revert, subject to the specific contract and route design. A wider permitted loss makes execution more likely to proceed after the market moves, but it also accepts a worse outcome. A narrow bound protects the treasury’s price limit more tightly, but can cause more failed attempts.

Do not treat “price impact” and “slippage” as synonyms. Price impact is the change caused by the trade’s size against available liquidity. Slippage is the difference between the expected and realized execution, which can include intervening market movement. A quote may show price impact in advance; the signed transaction’s minimum output governs whether additional movement is acceptable.

Which quote details should treasury operators check?

Operators should compare the net amount the destination must receive with the transaction’s actual execution bound. The headline exchange rate is not enough. Before signing, check that the quote and transaction agree on the assets, route, fee treatment and destination amount.

• Input and output assets: Confirm the exact token and network on each side, including whether the quoted output is an intermediate asset or the final asset the treasury needs.
• Net output and fees: Identify which fees are already deducted and which may be charged separately. Use the net receipt for policy and accounting checks.
• Minimum output: Compare the encoded floor with the treasury’s required receipt. A percentage tolerance is only a setting; the resulting floor is the operational limit.
• Quote freshness and route: Check whether the transaction still matches the latest quote and whether its route, spender and recipient are expected. Requote if the quote has expired or the assumptions have changed.

Simulation can catch some problems before submission, such as a transaction that currently reverts or returns less than the required minimum. It cannot guarantee that the state will remain unchanged until inclusion. Nor does a successful source-chain transaction prove that every later step of a cross-chain route has completed. Track each route’s status using its own settlement and recovery rules.

How should a treasury set its execution limit?

Set the minimum acceptable receipt from the treasury’s obligation, then reject any quote whose net output or executable floor falls below it. This reverses a common mistake: choosing a broad tolerance because a route failed, then discovering that the permitted output no longer meets the payment or accounting requirement.

If the transaction fails its minimum-output check, the intended outcome is generally a revert of that swap step, but cross-chain systems can have additional legs, refunds or recovery procedures. Check what the specific route does after each failure point before funding it. A new quote can resolve stale market assumptions, but it does not fix an incorrect recipient, inadequate allowance, unsupported token or missing recovery plan.

Treasury quotes move because liquidity, routing and execution conditions are live inputs. The practical control is to approve a net receipt and an execution floor that match the treasury’s requirement, then verify that the transaction submitted still enforces those limits.