DeFi / liquidity pool mechanics and risks
AMM liquidity pools: fees, risks and impermanent loss
Learn how LP pools differ from Binance Spot, separate fees from incentives, and reproduce a fictional LP-versus-HOLD calculation and risk checklist.
You will learn
- Distinguish an AMM liquidity position from Binance.com Spot, staking and lending.
- Separate potential swap fees, separate incentives, APR/APY assumptions, costs and absolute value changes.
- Recompute the stated fictional constant-product LP-versus-HOLD example and identify which pool-specific risks remain unverified.
Before you begin
Basic multiplication and division; no account, wallet connection, investment or transaction is needed.
A pool is not Binance Spot—and BNB Chain is not the Binance exchange
An automated market maker (AMM) lets a trader swap against token reserves managed by a smart contract, rather than submitting a buy or sell order to a central exchange order book. A liquidity provider (LP) supplies assets to that pool and may receive a version-specific position or claim. Binance.com Spot is an exchange product with its own trading pairs, order book, account balance and terms. A token shown on both screens is not automatically the same custody arrangement or transaction.
BNB Chain is a network ecosystem; BNB is an asset, and BNB Smart Chain (BSC) is one network in that ecosystem. If a particular protocol and pool are actually on BSC, the BNB Chain reference identifies native BNB as the network gas asset. That does not make Binance Spot and BSC the same service. This page does not verify a live PancakeSwap or other pool, token listing, account eligibility or regional access. Every protocol and version has its own code and rules.
Evidence: Uniswap pool, LP-share and version concepts · Binance.com Spot pair and account context · Centralized exchange order-book concept · BNB Smart Chain network role
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
Binance.com only; educational page may be outdated. Not a current UI walkthrough or regional rule.
Binance warns educational material may be outdated; only used for order book vs AMM distinction.
The overview also contains older performance, adoption and yield claims. This lesson uses only its identification of BSC as a network and BNB as its native gas asset; no fee amount, return or current service claim is inferred.
LP, staking and lending describe different arrangements
In a pool, you expose a pair of assets to swaps under the pool pricing mechanism. In Uniswap v2 the position is represented by a fungible pool token; Uniswap v3/v4 positions have a selected price range and different position accounting. Other protocols may use other records. The receipt or position is evidence of a protocol-specific claim, not a bank deposit or exchange Spot balance.
Staking participates in a network or protocol staking mechanism; lending supplies assets to a borrower or market under product-specific borrowing, interest and collateral rules. Neither is a synonym for LP. A farming program may add a separate incentive to an LP position, but that reward is not the same as staking BNB for network validation. Do not use one product fee, lock, redemption, tax or liquidation rules to infer another.
| Arrangement | What the supplied asset does | Potential compensation | A key distinction |
|---|---|---|---|
| AMM liquidity provision | Becomes part of a pool or defined LP position used by swaps | A share of eligible swap fees; sometimes separate incentives | Value and token mix change with pool trades; version and range matter |
| Binance.com Spot trade | A buy or sell order interacts with the exchange Spot market and account system | No LP share is implied by simply holding or trading in Spot | Exchange fees, execution and account terms are separate from an onchain pool |
| Staking or lending | Follows its own network/protocol or borrower/collateral rules | Protocol-defined rewards, interest or other terms, if any | Not a pool fee; may carry distinct lock, slashing, borrower or liquidation risks |
Evidence: Uniswap pool, LP-share and version concepts · PancakeSwap V2/V3 documentation · PancakeSwap V3 estimate and compounding distinctions · BNB Smart Chain network role · BSC network staking vs LP
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
Docs distinguish EVM and Solana; they do not prove current deployment, access or suitability.
Estimates rely on historic volume/current emissions that can change; no rate observed or copied.
The overview also contains older performance, adoption and yield claims. This lesson uses only its identification of BSC as a network and BNB as its native gas asset; no fee amount, return or current service claim is inferred.
Used only to distinguish BSC validator delegation from AMM liquidity provision. Its dated protocol details are not presented as current yields or product instructions.
What a pool can enable—and what an LP takes on
A pool can let swaps execute against pooled liquidity without waiting for a named buyer and seller to match in an order book. A provider may receive a proportional part of fees from swaps while its liquidity is active; a program may separately distribute incentives. These are possible functions of a design, not a promise that a particular pool exists, stays available, attracts volume or pays a positive net return.
The provider also accepts exposure to both assets, their relative prices, the pool contract and the chosen version. Adding or managing a position may require onchain transactions and network gas; claiming fees, changing a range or withdrawing can add costs. An incentive denominated in another token can change in value or stop. A displayed APR can use historical volume or planned emissions and may not include all costs, price changes, taxes, price-range inactivity or execution conditions.
| Possible fee or reward | Where it comes from | Questions before interpreting it |
|---|---|---|
| Swap fee | A fee charged on swaps, allocated according to protocol version and active liquidity | Which version, fee tier, active range, share formula and claiming/compounding rule? |
| Farm or token incentive | A separate program may distribute additional tokens | Who funds it, how can emissions change, when does it end, and what token risks apply? |
| APR estimate | An annualized display that may use a past period or current assumptions | Which inputs and time window; fees only or fees plus incentives; does it assume unchanged volume and price? |
| APY estimate | A compounded annualized result if rewards are reinvested at stated intervals | Are rewards actually reinvested, at what cost, and is the rate constant? It is a model, not a forecast. |
Evidence: Swap fees across Uniswap versions · PancakeSwap V3 estimate and compounding distinctions · PancakeSwap V2/V3 documentation
Version-specific fee collection/accounting; do not reuse rates or mechanics for other protocols.
Estimates rely on historic volume/current emissions that can change; no rate observed or copied.
Docs distinguish EVM and Solana; they do not prove current deployment, access or suitability.
A compounding example is arithmetic, not an offer
Suppose a fictional nominal APR is 12%, it stays constant for one year, the full reward is reinvested monthly, and there are no fees, gas, taxes or price changes. Then APY = (1 + 0.12 / 12)^12 - 1 = approximately 12.6825%. If rewards are not reinvested, or each reinvestment costs gas, this result does not describe the outcome. Real APR/APY labels can include different reward streams and assumptions.
PancakeSwap V3 documentation distinguishes estimated LP-fee APR from farm emissions and states that its displayed figures depend on historical trading volume or current emissions, can change and are not guaranteed. That page documents a PancakeSwap feature; it does not validate the fictional 12% rate or a current pool on BSC.
Evidence: PancakeSwap V3 estimate and compounding distinctions
Estimates rely on historic volume/current emissions that can change; no rate observed or copied.
Resolved example: divergence versus HOLD is not absolute profit or loss
Entirely hypothetical model: two invented assets A and S in a 50/50-by-value, full-range constant-product pool. Start with 5 A x $100 plus 500 S x $1 = $1,000. Assume S stays exactly at $1, no fees, gas, incentives, outside capital changes or borrowing, and idealized arbitrage adjusts the pool to the new relative price. The starting reserve product is k = 5 x 500 = 2,500 A*S. The symbol S is invented and does not represent a stablecoin, redemption promise or real-world peg.
Define r = (final A/S price) / (starting A/S price); r is a multiplier, not a price. If A rises to $200 while S remains $1, A/S moves from 100 to 200, so r = 2. For this model, x*y = 2,500 and y/x = 200, so x = sqrt(2,500/200) = 3.535534 A and y = 707.106781 S. The LP position is worth about $1,414.21. Holding the original 5 A and 500 S outside the pool would be worth $1,500. The LP is $85.79, or 5.7191%, below that HOLD comparison, yet its value is up $414.21, or 41.4214%, from the fictional $1,000 start. Those answers use different baselines.
For this particular 50/50, full-range constant-product model with no fees, LP value = $1,000 x sqrt(r); HOLD value = $500r + $500; relative divergence = LP/HOLD - 1 = 2sqrt(r)/(1+r) - 1. This describes relative position change, often called impermanent loss; it does not guarantee later recovery, and fees or incentives do not guarantee that it will beat HOLD. The separate both-assets-fall example below changes the assumption that S stays at $1.
| Final-to-initial A/S price multiplier r | LP value | Value of original assets held | LP vs HOLD | LP change vs $1,000 start |
|---|---|---|---|---|
| 0.25 | $500.00 | $625.00 | -20.0000% | -50.0000% |
| 0.5 | $707.11 | $750.00 | -5.7191% | -29.2893% |
| 1 | $1,000.00 | $1,000.00 | 0.0000% | 0.0000% |
| 2 | $1,414.21 | $1,500.00 | -5.7191% | +41.4214% |
| 4 | $2,000.00 | $2,500.00 | -20.0000% | +100.0000% |
Evidence: Uniswap pool, LP-share and version concepts · Historical constant-product and v2 oracle mechanics
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
Historical v2 technical description; protocol-fee discussion is not a current rate or status.
Separate hypothetical: both assets fall by half
Change the main example's stable-S assumption. In a separate fictional case, A falls from $100 to $50 and S falls from $1 to $0.50. Their relative A/S price stays at 100, the starting ratio, so r = (final A/S price) / (starting A/S price) = 1. With no fees or other changes, the pool position and the original HOLD basket are each worth $500: LP versus HOLD is 0%. Yet both are down $500, or 50%, from the fictional $1,000 starting value.
This case shows why zero divergence loss is not the same as zero absolute loss. The two falling prices are invented teaching inputs; S is not a real stablecoin, and this is not a market observation or forecast.
| Separate case | LP position value | Original assets held | LP vs HOLD | Change vs $1,000 start |
|---|---|---|---|---|
| A and S each fall 50% | $500.00 | $500.00 | 0.0000% | -50.0000% |
Evidence: Uniswap pool, LP-share and version concepts · Historical constant-product and v2 oracle mechanics
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
Historical v2 technical description; protocol-fee discussion is not a current rate or status.
Keep fee and cost assumptions outside the base calculation
As a separate hypothetical overlay at r = 2, add a final-value fee amount of $100 that was not included in the no-fee base, then subtract $15 of total costs valued in the same final unit. Net position value becomes $1,414.2136 + $100 - $15 = $1,499.2136, still about $0.7864 below the $1,500 HOLD value. This is not a simulated fee history or prediction.
Accounting matters: in a v2-style pool, fees can be added to reserves and affect the pool invariant. If an actual position value already includes those reserves or claimable fees, adding the same fees again double-counts them. Other versions may account for fees separately. Do not combine fee claims, token incentives, gas and market values without checking how the protocol records each item.
Evidence: Swap fees across Uniswap versions · Historical constant-product and v2 oracle mechanics
Version-specific fee collection/accounting; do not reuse rates or mechanics for other protocols.
Historical v2 technical description; protocol-fee discussion is not a current rate or status.
Full-range and concentrated positions behave differently
A full-range position in a simple constant-product model remains exposed across that model price curve. In Uniswap v3/v4 concentrated liquidity, the LP selects a finite price range. Concentrating capital can make more liquidity active within the selected interval, but position composition and fee activity depend on price staying in range. These are Uniswap version descriptions, not universal rules for every AMM.
If the price of a simple Uniswap v3/v4 pool moves outside its range, the position can become single-sided and stop earning fees until price returns; Uniswap support says that condition alone is not liquidation. This statement does not cover a borrowed or separately collateralized position. A range can remain out of range, so a period without fees is possible; monitoring and adjustments add attention and transaction costs.
| Model example | Range choice | What leaving the range means | Scope limit |
|---|---|---|---|
| Uniswap v2 concept | Liquidity distributed across the full curve | The position is not a custom finite range | Not every full-range or constant-product pool has the same fees or code |
| Uniswap v3/v4 concept | LP selects a finite interval | Outside range, a simple position can be single-sided and inactive for swap fees | Not a universal AMM rule; says nothing about borrowed-position liquidation |
| Other AMM or pool type | May use another curve, weighting or accounting | Read that pool own specification | Do not apply these equations without matching assumptions |
Evidence: Uniswap v3/v4 range mechanics · Uniswap v3/v4 simple position outside range · PancakeSwap V2/V3 documentation
Only Uniswap v3/v4 concepts; not full-range pools or other protocols.
Applies to the stated simple Uniswap v3/v4 position, not borrowed, leveraged or collateralized positions.
Docs distinguish EVM and Solana; they do not prove current deployment, access or suitability.
A risk checklist you can complete without connecting a wallet
A strong-looking APY, familiar logo or audit badge does not answer whether a particular pair is appropriate or safe. Before relying on a pool description, record the exact chain, pool contract, protocol/version, token contract addresses, position model and evidence date. If any cannot be verified from trustworthy sources, treat it as unknown and stop the analysis rather than depositing to find out.
Some risks apply only if that feature exists. A simple AMM does not necessarily use an external oracle; a pool does not necessarily contain a bridged asset; and a concentrated range does not automatically involve borrowing. A protocol may have admin roles or upgrade mechanisms. Verify the concrete code, controls and dependencies; do not infer them from a protocol name, a general audit report or this teaching example.
| Risk | Why it matters | Evidence to seek before relying on a claim | Unknown in this lesson |
|---|---|---|---|
| Relative price / divergence | Pool changes token mix as prices move; LP can trail holding initial tokens | Recompute LP and HOLD at same dates/unit and state the model | No future price, loss size or recovery path is known |
| Token, stablecoin or wrapper | A token can lose a target value, depend on a custodian/bridge, or differ from native asset | Check issuer/redemption if relevant, exact contract, origin and bridge dependencies | No A/S token, peg or issuer here is real or evaluated |
| Contract, admin or upgrade | Code defects or privileged controls can change behavior or access | Check deployed contract, verified code, version, admin/proxy/pause controls and audit scope/date | A protocol document or audit does not prove a deployment is safe |
| Oracle dependency | A linked application may use a pool-derived or external price; dependencies differ | Determine whether this pool or linked lending/derivatives app reads an oracle, and which | Not every AMM has an external oracle; no integration was examined |
| Bridge dependency | Cross-chain representations add bridge and asset-claim dependencies | Check native vs bridged asset, issuing bridge and route status | No bridge or current route is assumed |
| Ordering / MEV | Public onchain order flow can be reordered or used in arbitrage; execution may differ from quote | Check protocol transaction details, slippage controls and chain ordering docs | No transaction or user-level probability was measured |
| Range, exit and cost | Position can become one-sided or inactive; managing/removing it may require gas | Read exact version position accounting, fee claiming and withdrawal conditions | No universal instant withdrawal or continuous fees promised |
| Rewards and rate assumptions | Incentives can change/stop; APR may use past volume or current emissions | Separate swap fees from incentive tokens; identify period, compounding and costs | No live APR, pool availability or reward program checked |
Evidence: Uniswap pool, LP-share and version concepts · Historical constant-product and v2 oracle mechanics · PancakeSwap V2/V3 documentation · BSC transaction-ordering and MEV concepts
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
Historical v2 technical description; protocol-fee discussion is not a current rate or status.
Docs distinguish EVM and Solana; they do not prove current deployment, access or suitability.
Qualitative ordering-risk check only; no LP probability or loss estimate inferred.
A safe paper exercise and its solution
Without opening an app, take the r = 2 row and answer: (1) What does -5.7191% compare? (2) Did the fictional LP lose value versus its initial $1,000? (3) Can you add the separate $100 fee assumption twice? (4) Does the arithmetic prove that a specific BNB Chain pool exists?
Solved: (1) It compares the LP position with keeping the original 5 A and 500 S; (2) no, the model LP value rose 41.4214% from $1,000 even though it lagged HOLD; (3) no, add fees once and only if excluded from the position value; (4) no. The model establishes no pool, token contract, access, rate or result. A real analysis still needs documentation for the exact pool and current onchain/product evidence.
Evidence: Uniswap pool, LP-share and version concepts · Swap fees across Uniswap versions · BNB Smart Chain network role
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
Version-specific fee collection/accounting; do not reuse rates or mechanics for other protocols.
The overview also contains older performance, adoption and yield claims. This lesson uses only its identification of BSC as a network and BNB as its native gas asset; no fee amount, return or current service claim is inferred.
Check your understanding
With r = 2, why can the fictional LP be 5.7191% below HOLD and still be up 41.4214% from its starting value?
Show explanation
The first percentage compares the $1,414.21 LP position with the $1,500 value of holding the original assets. The second compares that LP position with its $1,000 starting value. The baselines differ. This is hypothetical arithmetic, not a prediction.
Primary sources
- How Uniswap WorksUniswap Developers · 2026-10-26
Uniswap-specific; version mechanics are not universal and do not prove any pool is live.
- FeesUniswap Developers · 2026-10-26
Version-specific fee collection/accounting; do not reuse rates or mechanics for other protocols.
- Concentrated LiquidityUniswap Developers · 2026-10-26
Only Uniswap v3/v4 concepts; not full-range pools or other protocols.
- Uniswap v2 Core whitepaper (March 2020)Uniswap · 2026-10-26
Historical v2 technical description; protocol-fee discussion is not a current rate or status.
- Do I get liquidated if the price goes outside of my range?Uniswap Labs Support · 2026-10-26
Applies to the stated simple Uniswap v3/v4 position, not borrowed, leveraged or collateralized positions.
- Liquidity PoolsPancakeSwap Documentation · 2026-10-26
Docs distinguish EVM and Solana; they do not prove current deployment, access or suitability.
- APR/ROI/IL CalculatorPancakeSwap Documentation · 2026-10-26
Estimates rely on historic volume/current emissions that can change; no rate observed or copied.
- How to Add/Remove Liquidity (EVM)PancakeSwap Documentation · 2026-10-26
Documentation only; no interface, pool, account, wallet or transaction tested; withdrawal claims are not generalized.
- Understanding Order Book and Market DepthBinance Support · 2026-10-26
Binance warns educational material may be outdated; only used for order book vs AMM distinction.
- How to Spot Trade on Binance Website?Binance Support · 2026-10-26
Binance.com only; educational page may be outdated. Not a current UI walkthrough or regional rule.
- BSC MEV OverviewBNB Chain · 2026-10-26
Qualitative ordering-risk check only; no LP probability or loss estimate inferred.
- BNB Smart Chain overview (only network role checked 2026-10-26)BNB Chain · 2026-10-26
The overview also contains older performance, adoption and yield claims. This lesson uses only its identification of BSC as a network and BNB as its native gas asset; no fee amount, return or current service claim is inferred.
- BSC Staking OverviewBNB Chain · 2026-10-26
Used only to distinguish BSC validator delegation from AMM liquidity provision. Its dated protocol details are not presented as current yields or product instructions.