
DeFi swaps: slippage, price impact, and minimum received
Use a worked example to separate price impact from slippage tolerance and understand what a minimum-received setting actually protects.
Know the route. Know the boundary.
The number on screen is only the beginning. Understand the route, the boundary you authorize, and the difference between a quote and a completed exchange.
A swap estimate belongs to a particular pair of assets, network, input size, route, and moment. Confirm all five before comparing the output. A familiar token name does not establish identity, and a small test quote does not establish pricing for a much larger exchange.
Look for intermediate assets and protocols in the route. An additional step can change both execution and dependencies. Ask what the route does rather than assuming a single button means a single simple market.
Price impact describes the trade’s effect on available pricing. It can already be reflected in the quote. Slippage concerns changes between the quoted conditions and execution. A setting that controls tolerated deterioration does not undo price impact or create more liquidity.
For an exact-input trade, a minimum-received constraint expresses a lower boundary for output under the transaction’s implementation. It is not a promise that the first quoted amount will arrive, nor a guarantee about the value or quality of the output token.
A quoted output may already include trading charges while excluding a separate network fee. Read those labels before subtracting a fee twice or overlooking it entirely. Use a consistent reference valuation when comparing costs charged in different assets.
The worked guide below uses invented numbers to show the arithmetic. They are not current gas prices, suggested tolerances, or a prediction about a particular market. The purpose is to understand which values are included in the comparison.
An authorization to spend a token can be a separate action from the exchange. Inspect the spender, token, amount, and scope. A carefully chosen minimum output does not protect against an unrelated permission you also signed.
If execution fails, investigate the recorded status before retrying or widening tolerance. A price-related boundary is only one possible cause. The correct response depends on the actual error and whether the original transaction changed state.
The assets a trader exchanges come from a particular market design. A liquidity provider’s position can change composition as trades occur. Fee income is only one component of that position’s result; comparing it with simply holding requires complete accounting.
Our liquidity-pool article uses a clearly defined 50/50 model, then explains why it should not be copied into every pool design. Read both sides of the exchange to understand the mechanics without assuming the same risks apply to traders and providers.
A little more clarity
Start with the mechanics. Keep the limits in view.
No. It defines an acceptable execution boundary under the selected transaction design. It is separate from trading charges and network costs.
No. It constrains token output, not asset identity, investment value, route quality, or every separate cost. Those checks still matter.