How to Exit a Liquidity Position

Exiting a liquidity position returns tokens in the current pool ratio, not your entry ratio — and impermanent loss crystallizes at exit. Here's how the mechanic works across v2, v3, and Curve pools.
Lewis Jackson
CEO and Founder

Exiting a liquidity position isn't just clicking "remove" and getting your tokens back. The mechanics are different enough from a standard transfer or swap that users regularly get surprised by what they receive — particularly the first time.

The confusion usually comes down to two things. First, you receive tokens in the current pool ratio, not the ratio you deposited. Second, impermanent loss crystallizes at exit, meaning the full accounting of price divergence happens when you leave.

Understanding those two points before you exit saves most of the surprises.

How the Exit Works in v2 Pools

Uniswap v2-style pools — and most AMMs that use the constant-product formula — represent your position as fungible LP tokens. You deposit two assets, you receive LP tokens proportional to your share of the pool. Exiting reverses that process.

The steps:

  1. You select what percentage of your LP tokens to withdraw — 25%, 50%, 100%, whatever you want
  2. The protocol burns those tokens and calculates your current share of pool reserves
  3. You receive both assets in the ratio the pool holds them right now

That third step is where it gets interesting. If you entered an ETH/USDC pool when ETH was trading at $1,800, and you're exiting when ETH is at $2,400, the AMM has been continuously rebalancing your position as prices moved. You'll receive less ETH and more USDC than you originally deposited. That's the constant-product formula doing what it's designed to do — and it's also impermanent loss becoming permanent.

Trading fees accumulate separately and are returned at exit. They partially offset the impermanent loss, depending on how much volume ran through the pool while you were in it.

V3 Positions Are More Complex

Concentrated liquidity positions — Uniswap v3 and protocols that copied the design — add a layer of complexity. Your position is an NFT representing a specific price range, not a fungible share of the entire pool.

Two things change at exit.

First, collecting fees is a separate transaction from removing liquidity. The Uniswap v3 interface includes a checkbox to collect fees alongside the removal, so you can do both in one flow — but they're separate under the hood. If the checkbox is unchecked or the flow fails after removal but before fee collection, those fees are lost. Worth verifying before confirming.

Second, if the current price is outside your configured range, your position is 100% in one token. Say you set a range of $1,800–$2,200 for ETH/USDC and ETH now trades at $2,500. Everything you had is in USDC at this point — the AMM converted all your ETH as the price moved through your range and kept going. You exit with USDC, not a split.

This catches people off guard. A "50/50 position" at entry doesn't stay 50/50 as prices move. When you're fully out of range on either side, you've essentially been auto-converted.

Curve and Balancer Are Different Again

Curve's stableswap pools give you more flexibility at exit: you can receive any of the pool's constituent tokens, not just a proportional split. This sounds good, but it means you're implicitly doing a swap at exit. A balanced exit (proportional across all tokens) has minimal price impact; exiting 100% into a single token hits the pool's current imbalance and produces more slippage.

For most stablecoin pools this is negligible. For a pool that's heavily imbalanced toward one stablecoin, it matters more.

Balancer has similar flexibility depending on pool type — weighted pools, boosted pools, and composable pools all have slightly different exit mechanics. The protocol surfaces the estimated output before you confirm, but knowing whether you're in a standard or boosted pool is useful context for interpreting what you see.

What Determines What You Receive

Across all AMM types, your exit proceeds depend on:

  • Current pool reserves at the moment of exit (not what they were when you entered)
  • Your share of those reserves
  • Accumulated fees from trading activity while you were in the pool
  • Protocol fees if the pool deducts any at exit (most v2-style pools don't, but some do)

You won't know the exact dollar outcome until you compare entry cost to exit proceeds — and that comparison requires knowing your original deposit values, not just the token amounts.

The Gas Cost Problem on Small Positions

Gas is a flat cost, not proportional to position size. Exiting a v3 position on Ethereum mainnet — especially with a separate fee collection transaction — can cost $15–$40 during moderate congestion. That matters a lot on a $300 position. Not at all on a $30,000 position.

Most LP activity has moved to L2s for this reason. Exit transactions on Arbitrum, Optimism, or Base are typically a few dollars. If you're managing positions on mainnet, exit timing around low-congestion windows (weekends, off-peak hours) is worth the few dollars it saves.

Some protocols also have liquidity lock mechanisms on incentivized pools — usually a short vesting period before exit is permitted. These are disclosed at deposit, but easy to overlook if you're moving quickly.

What's Changing

The broader direction is toward better tooling. Uniswap has iterated its v3 exit interface significantly since v3 launched. Third-party position managers — Revert Finance, Gamma, Arrakis — provide cleaner readouts of impermanent loss and fee income than the base protocol UI, which helps with exit timing decisions.

Cross-chain liquidity positions are still early. Some protocols let you deposit into a strategy that spans multiple chains; exit mechanics for these vary and are often less documented than their entry flows. Treat them with extra scrutiny.

Confirmation and Invalidation

The fundamentals here are stable — the AMM math doesn't change. What does change is whether UIs surface the necessary information clearly enough that users don't get surprised by token ratios at exit.

The main risk isn't the mechanism. It's depositing into a pool with exit constraints you didn't check — a liquidity lock, a withdrawal fee, or a protocol where exit requires passing through a governance queue.

Timing

Now: Before confirming any v3 exit, verify that fee collection is included in the transaction — or run it as a separate step first. The Uniswap interface makes this easy to overlook.

Next: If you're actively managing multiple positions, a dashboard that tracks fee income vs impermanent loss in real time (Revert Finance does this well) is worth setting up before you need to make exit decisions, not during.

Later: Unified position management across chains — enter once, manage across L2s — is the direction the ecosystem is moving, but the exit tooling for those strategies isn't fully mature. Worth waiting for.

Boundary

This covers the mechanics of removing liquidity from AMM pools. It doesn't address the tax treatment of LP exits in any jurisdiction, impermanent loss calculations in detail, or the exit mechanics for lending protocols like Aave or Compound, which operate differently from AMM liquidity provision entirely.

Related Posts

See All
Crypto Research
New XRP-Focused Research Defining the “Velocity Threshold” for Global Settlement and Liquidity
A lot of people looking at my recent research have asked the same question: “Surely Ripple already understands all of this. So what does that mean for XRP?” That question is completely valid — and it turns out it’s the right question to ask. This research breaks down why XRP is unlikely to be the internal settlement asset of CBDC shared ledgers or unified bank platforms, and why that doesn’t mean XRP is irrelevant. Instead, it explains where XRP realistically fits in the system banks are actually building: at the seams, where different rulebooks, platforms, and networks still need to connect. Using liquidity math, system design, and real-world settlement mechanics, this piece explains: why most value settles inside venues, not through bridges why XRP’s role is narrower but more precise than most narratives suggest how velocity (refresh interval) determines whether XRP creates scarcity or just throughput and why Ripple’s strategy makes more sense once you stop assuming XRP must be “the core of everything” This isn’t a bullish or bearish take — it’s a structural one. If you want to understand XRP beyond hype and price targets, this is the question you need to grapple with.
Read Now
Crypto Research
The Jackson Liquidity Framework - Announcement
Lewis Jackson Ventures announces the release of the Jackson Liquidity Framework — the first quantitative, regulator-aligned model for liquidity sizing in AMM-based settlement systems, CBDC corridors, and tokenised financial infrastructures. Developed using advanced stochastic simulations and grounded in Basel III and PFMI principles, the framework provides a missing methodology for determining how much liquidity prefunded AMM pools actually require under real-world flow conditions.
Read Now
Crypto Research
Banks, Stablecoins, and Tokenized Assets
In Episode 011 of The Macro, crypto analyst Lewis Jackson unpacks a pivotal week in global finance — one marked by record growth in tokenized assets, expanding stablecoin adoption across emerging markets, and major institutions deepening their blockchain commitments. This research brief summarises Jackson’s key findings, from tokenized deposits to institutional RWA chains and AI-driven compliance, and explains how these developments signal a maturing, multi-rail settlement architecture spanning Ethereum, XRPL, stablecoin networks, and new interoperability layers.Taken together, this episode marks a structural shift toward programmable finance, instant settlement, and tokenized real-world assets at global scale.
Read Now

Related Posts

See All
No items found.
Lewsletter

Weekly notes on what I’m seeing

A personal letter I send straight to your inbox —reflections on crypto, wealth, time and life.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.