Why Wallet Swap Quotes Differ From the Amount You Receive

A wallet swap can deliver less than its quote because the quote estimates an output, while the transaction executes against liquidity that may change before it is included. The displayed amount is not a guaranteed fill unless the wallet or swap contract enforces it as a minimum. To understand the difference, separate the quoted output, execution price, deductions and transaction cost.

What does a swap quote actually represent?

A swap quote is a calculation of the output available for a specified input under the routing conditions observed when the wallet requests it. A wallet may query one pool or compare routes through several pools and tokens. Each route has its own available liquidity and price. The best route is usually the one that estimates the largest output after the swap fees it accounts for, but that estimate can become stale.

In a constant-product pool, a trade changes the ratio of the pool’s assets. A larger input therefore moves the price against the trader as it consumes liquidity. This effect is price impact: it is caused by the trade itself, even if the pool state does not change between quote and execution. Thin liquidity or a large trade relative to the pool makes the impact greater. A route split across pools can reduce that effect, but may add more swap steps and fees.

Route choice also depends on which assets and pools the system supports. For a focused explanation of checking supported assets before a swap, see chainflip. Support and routing availability are separate from the price guarantee: a valid route can still execute at a different rate than the one quoted.

Why can the execution price change after I accept?

The transaction does not reserve the quoted pool state when the wallet displays it. Other swaps can be confirmed first, changing reserves and the rate available to the transaction. The transaction also waits for inclusion, so the quote may age while network conditions or pool balances move. When it executes, the contract evaluates the swap against the state that exists then.

The wallet’s slippage tolerance sets how much the received output may fall below the quote before the transaction reverts, if the swap route implements a minimum-output condition. The minimum is commonly derived from the quoted output and the selected tolerance. It is a boundary, not a promise that execution will land near the quote. If the output is below that boundary, the swap fails instead of completing at the worse rate; the user may still pay network fees for the reverted transaction.

Some systems express protection as a minimum amount out, while others use a price limit or a different route-specific condition. Read the transaction review and wallet settings to identify the actual constraint. A displayed percentage alone does not establish what the contract checks.

Which costs reduce the amount I receive?

Several amounts can appear around one swap, and they do not all reduce the same figure. The quoted output may already account for pool fees and routing costs, while network gas is typically paid separately in the chain’s fee asset. A wallet may also display a net estimate that subtracts some charges from the output, so compare like with like.

• Pool fee: charged by a liquidity pool and reflected in the swap calculation, depending on the quote interface.
• Price impact: the rate movement caused by the size of the trade against available liquidity.
• Route costs: additional pool fees or other deductions from using multiple steps.
• Network fee: paid to have the transaction processed; it is generally separate from the swap output.

Token mechanics can add another difference. A token may apply a transfer fee or other contract behavior, so the amount credited to the recipient can differ from the amount a router calculates as output. Do not assume every token is a standard transfer. The wallet’s displayed estimate may not model every token-specific behavior.

How can I tell whether a lower amount is expected?

Compare the quoted output with the transaction’s minimum-output condition and the amount actually received. If the transaction succeeded and the received amount is at or above its enforced minimum, it met that constraint even if it fell short of the quote. The gap can reflect price impact, a changed pool state, route execution or token transfer behavior. A separate gas charge explains a higher total cost, but does not by itself mean fewer output tokens were delivered.

Before signing, check the input amount, estimated output, route details if shown, slippage setting, minimum received and network fee. For a large trade, compare the estimated output at different input sizes; a sharp decline can indicate material price impact. If the route or minimum is unclear, do not treat the headline quote as a guarantee.

The practical comparison is the amount you expect to receive after swap-related deductions, the minimum the transaction permits, and the separate cost to execute it. A quote is useful for comparing routes at a moment in time. The minimum-output condition is what limits execution when the market moves before confirmation.