Skip to content
PANTHER

Minimum Received: The Swap Number You’re Agreeing To

A small slippage percentage can sit beside a costly quote. Read the output floor, distinguish exact-input from exact-output swaps and check what the limit leaves out.

By Panther@0xPnthr

5 min read

Conceptual minimum-received illustration: a translucent glass slab floats above a solid white stop on a black background, with READ THE MINIMUM and Panther Knowledge text.
Illustration: Panther, created with ChatGPT. Conceptual artwork, not a quantitative chart or trading interface.

Key points

  • Minimum received is an output floor for an exact-input swap, not a guarantee of the quoted amount or a fair exchange rate.
  • A tight slippage limit does not remove price impact or costs already reflected in the quote.
  • Exact-output swaps bound maximum input; routing modes and fee treatment must be checked separately.

Minimum received is the swap detail to read before pressing Confirm. The quote can look attractive, the slippage percentage can look small, and the transaction can still authorize an outcome you would not choose if the token amount were written in large type.

For a conventional exact-input swap with an enforced output limit, minimum received is the least output the transaction will accept. A quote describes an expected result. The minimum defines the boundary. Neither number, by itself, tells you the trade’s full economic cost.

This guide is a practical quote audit: how to read that floor, compare it with the expected output and recognize when changing slippage answers the wrong question.

What minimum received actually controls

An exact-input swap fixes how much of the input token you spend and lets the output vary within the transaction’s constraints. Uniswap’s developer explanation of swap protections describes amountOutMinimum: execution reverts if the swap would return less than the specified output.

That is a condition on execution, not a promise that the displayed quote will be delivered. A result above the floor can satisfy this particular check while still being worse than the quote. Other checks can also make the transaction fail.

Read the minimum as a quantity of the token you intend to receive. A familiar symbol or a fiat estimate can distract from the actual asset and units. Panther’s contract-address guide covers verifying that identity before comparing prices.

A small slippage setting does not repair an expensive quote

Uniswap’s price-impact comparison separates two concepts. Price impact comes from your own trade. Slippage concerns the difference between the expected and realized swap price.

If your proposed size already produces an unattractive quote, tightening the permitted movement around that quote does not turn it into a competitive one. Conversely, widening the tolerance does not add liquidity or improve the quoted exchange rate.

The price-impact documentation links impact to trade size relative to available liquidity. Compare fresh quotes for different sizes and supported routes before deciding whether to proceed. The purpose is to understand the exchange rate you are accepting, not merely to remove a warning.

Panther’s market-cap and liquidity guide explains pool depth. This guide starts at the next decision: the output boundary encoded for your particular swap.

Worked example: 1% around a quote is not 1% against every benchmark

Hypothetical arithmetic, not a live quote, token recommendation or executed trade. Fees, taxes, rounding and network costs are excluded to isolate the comparison.

Suppose an independent reference rate would give 10,000 units of Token B for your chosen input. The route you are considering instead quotes 9,500 units. You then choose an illustrative acceptance policy allowing output as low as 9,405 units: 1% below that quoted amount.

Number being compared Output in Token B Shortfall from the 10,000-unit reference
Reference-rate benchmark 10,000 None
Route’s quoted output 9,500 500 units, or 5%
Chosen minimum output 9,405 595 units, or 5.95%

The extra allowance below the quote is 95 units. It does not erase the 500-unit gap already present when the quote was offered. The combined shortfall at the floor is 5.95%, rather than the 1% setting viewed in isolation.

This is deliberately a chosen output-floor example. Interfaces and routing systems can calculate percentage tolerances differently, including price conventions and integer rounding. Read the actual minimum displayed or encoded; do not use this example as a universal formula for every app.

The reference also needs scrutiny. A price from another venue may be stale, inaccessible for your size or exclude costs. A quoted gap is a reason to investigate the comparison, not automatic proof of misconduct.

Exact-output swaps reverse the question

When you request a fixed output, the relevant bound is typically the maximum input you permit. Uniswap’s quote API reference explicitly distinguishes output-token slippage for exact-input trades from input-token slippage for exact-output trades.

That difference changes the review. “Receive at least this much” and “spend no more than this much” protect different sides of the exchange. Identify which amount is fixed before interpreting a percentage.

The same reference warns that slippage behaves differently for UniswapX. A setting in one routing mode should not be assumed to govern another mode’s spread. Check the order’s actual terms and minimum amount when the app changes its execution route.

Find the floor and read the other costs beside it

The Uniswap Web App field guide separates fees, network cost, routing, price impact and maximum slippage. Its maximum-slippage detail exposes the minimum output. Labels and navigation can change; expand the current swap details instead of relying on a remembered default.

On Solana, Jupiter’s Metis integration guide provides a concrete developer example. It describes outAmount as expected output after AMM and platform fees, and otherAmountThreshold as the minimum acceptable output after slippage tolerance. That description belongs to the documented flow, not every product with a Jupiter label.

For builders, keep raw token units, decimals and percentage units distinct. Jupiter’s cited guide expresses slippage in basis points: 50 basis points equals 0.5%. A setting labeled 50 must not silently be treated as 50%.

For users, compare like with like: same input amount, output asset, network and quote time. Establish which costs are included in the output and which are charged separately. A token-output floor alone is not a cap on every expense associated with the trade.

A failed swap is a diagnosis, not an instruction to widen the limit

Uniswap’s slippage settings guidance explains the trade-off: a tight limit may cause failure, while a wide limit can allow fewer tokens than expected. There is no single percentage this guide recommends for every pair and trade size.

Jupiter’s error reference separately identifies missing routes, unavailable markets, amount-threshold problems and transaction-composition failures. Those conditions should not all receive the same “increase slippage” response.

Refresh the quote, read the actual error and compare the new floor before signing another attempt. If a send has already been submitted, establish its status first. The Solana transfer-failure guide explains how to avoid confusing a wallet notification with a confirmed outcome.

The final review before signing

Ask four questions: Is this the intended asset? Is the quote acceptable for this size? Is the minimum output—or maximum input—an outcome I would actually accept? What costs sit outside that number?

If the answers are unclear, stop at the review screen. Completing the swap is not the objective of a price-protection setting. Completing it within terms you understand is.

Sources and verification

Reviewed against the linked Uniswap Labs and Jupiter documentation on November 12, 2026. The table and calculations are original illustrative analysis, not observed market data. No wallet was connected and no swap or recovery test was performed. The scope is swap execution limits; token safety and MEV require additional checks, covered in Panther’s sandwich-attack guide.

Sources

  1. 01Understanding swaps and execution protections · Uniswap Developersdevelopers.uniswap.org/docs/get-started/concepts/traders/swaps
  2. 02Price impact versus slippage · Uniswap Labssupport.uniswap.org/hc/en-us/articles/8643794102669-Price-Impact-vs-Price-Slippage
  3. 03Quote API: exact input, exact output and routing · Uniswap Developersdevelopers.uniswap.org/docs/api-reference/aggregator_quote
  4. 04Uniswap Web App swap-screen fields · Uniswap Labssupport.uniswap.org/hc/en-us/articles/39862756339341-Uniswap-Web-App-The-Swap-Screen
  5. 05Metis custom-swap quote fields · Jupiter Developersdevelopers.jup.ag/docs/guides/how-to-build-a-custom-swap-with-metis
  6. 06Swap error reference · Jupiter Developersdevelopers.jup.ag/docs/swap/v1/common-errors

Responses

Links, wallet addresses and contact details are not allowed.

0/1000

No responses yet. Start the conversation.

Panther Journal — The intelligence brief

Stay ahead of the story.

Free. New investigations delivered when published. Unsubscribe anytime.

Launching something?

Work directly with Panther.

Start a project

More from the library