Just-In-Time (JIT) liquidity extraction is a structural cost borne by passive liquidity providers in Uniswap V3's concentrated liquidity architecture. MEV searchers atomically mint and burn extremely narrow-range liquidity positions within a single block, capturing a disproportionate share of swap fees from pending transactions without bearing the inventory risk or divergence loss that passive LPs incur. This extraction is not a bug or exploit—it is a rational response to the fee mechanics and mempool transparency that define the Ethereum execution environment.

Quantifying JIT Impact on Passive LP Returns
Introduction
Quantifying how Just-In-Time liquidity bots siphon swap fees from passive LPs in Uniswap V3 pools, segmented by pool characteristics and market conditions.
The practical impact on LP returns varies significantly across pool types. High-volume, low-fee-tier pools with predictable swap flow are the most heavily targeted. Empirical measurement methodologies—including Dune Analytics dashboards, EigenPhi's MEV explorer, and custom node-level simulations—consistently show that JIT bots can capture 10-30% of total swap fees in vulnerable pools during periods of elevated mempool visibility. For passive LPs, this represents a direct reduction in fee APR that is not offset by any compensating benefit, effectively acting as a hidden tax on liquidity provision.
LP operators and risk teams must incorporate JIT extraction into their return models when evaluating whether a pool is economically viable. A pool that appears profitable based on gross fee generation may become net-negative after accounting for JIT leakage, particularly when combined with loss-versus-rebalancing (LVR). The measurement challenge is non-trivial: JIT transactions are structurally identical to normal mint-burn-swap sequences and require heuristic identification based on position duration, tick range width, and atomic execution patterns. Teams that fail to account for this extraction risk over-allocating capital to pools where passive returns are structurally impaired.
Chainscore Labs helps LP operators and protocol teams quantify JIT extraction exposure across their active pool positions, validate measurement methodologies against on-chain data, and design parameter choices—including fee-tier selection and rebalancing frequency—that minimize the fraction of returns lost to JIT bots. For protocols building on Uniswap V4, we assess whether custom hook logic can serve as a credible mitigation layer without introducing new attack surfaces or composability breaks.
Quick Facts
Operational facts for LP operators and risk teams quantifying how Just-In-Time liquidity extraction reduces passive LP fee revenue across Uniswap V3 pools.
| Field | Value | Why it matters |
|---|---|---|
Extraction mechanism | MEV searchers atomically mint and burn concentrated liquidity within a single block to capture swap fees without bearing inventory risk. | Passive LPs lose fee revenue to actors who contribute no continuous liquidity, skewing expected return calculations. |
Primary targets | High-volume stablecoin pairs and ETH/USDC pools with low fee tiers (1-5 bps) and moderate volatility. | LP operators must identify which pools are uneconomical due to JIT extraction before committing capital. |
Measured fee loss range | Studies estimate 20-40% of swap fees can be extracted by JIT bots in vulnerable pools, varying by TVL and volatility regime. | Return projections that ignore JIT extraction overstate passive LP profitability by a material margin. |
Measurement methodology | Compare on-chain fee accrual of static LP positions against total pool fees, isolating atomic mint-burn sequences within single blocks. | Risk teams need a reproducible methodology to audit pool-level extraction rates before deploying capital. |
Data sources | EigenPhi, MEV-inspect, and custom Dune dashboards indexing atomic V3 mint-burn events correlated with swap activity. | Operators must integrate these data pipelines to monitor JIT extraction rates in real time for active positions. |
Pool characteristics that amplify JIT | Low TVL pools with high relative volume, narrow tick ranges, and low fee tiers create the most extractable fee surface. | LP strategists should avoid or dynamically manage positions in pools with these characteristics unless actively hedging. |
Mitigation strategies | V4 hooks enabling dynamic fees, auction-based fee mechanisms, or minimum liquidity duration requirements can reduce JIT viability. | Protocol architects and governance participants evaluating V4 hook designs must assess JIT resistance as a core LP protection feature. |
Impact on LP profitability models | Standard LVR and fee-revenue equilibrium models must incorporate a JIT extraction discount to produce accurate break-even estimates. | Institutional LPs using these models without a JIT adjustment layer will systematically over-allocate to vulnerable pools. |
Technical Mechanism of JIT Extraction
How MEV searchers atomically mint and burn Uniswap V3 liquidity within a single block to capture swap fees without bearing inventory risk.
Just-in-time (JIT) liquidity extraction on Uniswap V3 is an MEV strategy where a searcher observes a pending swap in the mempool, atomically mints a highly concentrated liquidity position around the expected execution price, collects the swap fees, and burns the position—all within a single transaction block. This is possible because Uniswap V3's concentrated liquidity model allows LPs to provide capital within arbitrarily narrow price ranges (tickLower to tickUpper), and the multicall pattern enables minting, swap execution, and burning to be bundled into one atomic transaction via a custom contract or proxy. The searcher never holds the LP position across blocks, eliminating inventory risk entirely while capturing a disproportionate share of the swap fees that would otherwise accrue to passive LPs.
The extraction works by targeting pending swap transactions in the public mempool. The searcher simulates the swap's price impact, calculates the exact tick range that will be crossed, and mints a position with liquidity concentrated precisely within that range. The searcher's transaction is ordered immediately before the target swap (via priority gas auction or builder relationships), so the minted position is active when the swap executes. The swap crosses the searcher's tick range, generating fees that flow to the JIT position. In the same atomic transaction, the searcher burns the position and recovers the principal plus fees. The passive LPs who provided liquidity across wider ranges receive a reduced share of the swap fees, as the JIT position effectively front-runs their fee accrual without contributing to long-term pool depth.
Pools with higher fee tiers (1% and 0.3%) and moderate-to-high volatility are the most attractive targets, as the fee capture per swap is larger and the price range can be predicted with sufficient accuracy from mempool visibility. The strategy is less effective in low-fee tiers (0.05%, 0.01%) where gas costs can exceed the extracted fees, and in extremely volatile conditions where price prediction becomes unreliable. For passive LP operators, JIT extraction represents a structural drag on returns that is not captured by standard impermanent loss or LVR models. Teams assessing LP profitability should incorporate JIT extraction estimates—particularly for pools in the 0.3% and 1% fee tiers with observable mempool activity—and consider whether the net fee yield after extraction justifies the capital deployment. Chainscore Labs can help LP operators quantify JIT impact on specific pool positions and evaluate mitigation strategies such as private order flow routing or hook-based fee redistribution mechanisms.
Affected Actors
Passive Liquidity Providers
Passive LPs are the primary victims of JIT extraction. Bots atomically mint and burn concentrated liquidity positions within a single block, capturing swap fees that would otherwise accrue to existing LPs. This directly reduces the fee APR that passive LPs earn.
Impact severity varies by pool:
- Low-fee tiers (0.01%, 0.05%) with high volume see the highest percentage of fees extracted
- Pools with wide tick spacing and low TVL concentration are more vulnerable
- Stablecoin pairs and ETH-stablecoin pairs are prime JIT targets
Action items:
- Recalculate expected returns using JIT-adjusted fee models before committing capital
- Monitor fee capture rates on active positions; if JIT extraction exceeds 30% of fees, the pool may be uneconomical
- Consider migrating to higher-fee tiers where JIT bots face tighter profit margins
- Evaluate V4 hook-based mitigation strategies as they become available
Measurement Methodology and Data Sources
A rigorous methodology for measuring JIT impact requires precise data sourcing, careful statistical framing, and an understanding of the inherent limitations in on-chain analysis.
Atomic Mint-Burn Identification
The core methodology involves scanning each block for transactions that call both the NonfungiblePositionManager's mint and burn functions for the same pool within a single atomic transaction. This pattern is the definitive on-chain signature of a JIT attack. Analysts must filter out noise from failed transactions or complex MEV bundles that include extraneous operations. The output is a dataset of JIT positions, each linked to a specific block, pool, tick range, and liquidity amount, forming the basis for all subsequent fee extraction calculations.
Fee Accrual Calculation Model
To quantify the fees captured by a JIT position, one must simulate the swap activity that occurred within the block after the JIT liquidity was minted but before it was burned. This requires replaying the exact sequence of swaps in the block against the pool's state, including the JIT position's liquidity. The fees earned by the JIT position are calculated by comparing its fee growth inside the tick range at burn time versus mint time. This model isolates the fees that would have otherwise accrued to passive LPs in the same tick range.
Passive LP Counterfactual Baseline
The impact on passive LPs is measured by constructing a counterfactual: what fees would the passive position have earned if the JIT liquidity had not been present? This is not simply the JIT's collected fees, as the JIT liquidity itself changes the pool's marginal price impact and fee distribution. A precise model simulates the same swap sequence against the pool state without the JIT position, calculating the additional fees that flow to the passive position's tick range. The difference represents the true extraction from passive LPs.
Data Source Architecture
A robust measurement pipeline requires an archive node with tracing capabilities (e.g., Erigon, Reth) to replay historical blocks and access internal contract state. The primary data sources are the Uniswap V3 Pool and NonfungiblePositionManager contract events. Analysts must index all Mint, Burn, and Swap events, and use eth_call or debug traces to query feeGrowthInside0LastX128 and feeGrowthInside1LastX128 values at specific block heights. For cross-pool analysis, a dedicated ETL pipeline that transforms raw event logs into a queryable relational model is essential.
Segmentation and Statistical Controls
Raw extraction percentages are meaningless without segmentation. Analysis must control for pool fee tier (5, 30, 100 bps), TVL, and volatility regime. A JIT attack on a 5 bps stablecoin pool extracts a different fee share than one on a 100 bps exotic pair pool. Statistical models should segment data by these dimensions and report median and tail extraction rates. Volatility can be proxied using the pool's own TWAP or an external oracle. This segmentation reveals which pool archetypes are uneconomical for passive LPs due to JIT extraction.
Methodological Limitations and Blind Spots
On-chain analysis cannot capture private mempool transactions or off-chain order flow auctions like UniswapX, where JIT-like behavior may occur without a visible on-chain mint-burn pair. The counterfactual model assumes atomicity and perfect information, which may overstate extraction if the JIT bot's presence deters other arbitrageurs. Furthermore, the analysis does not account for the potential positive effect of JIT on reducing passive LP divergence loss by tightening the spread. Teams should treat these measurements as a lower bound on extraction and verify findings against multiple independent data pipelines.
JIT Impact Segmentation Matrix
How JIT extraction severity varies across pool types and what each affected group should monitor or adjust
| Pool Segment | JIT Extraction Profile | Who is affected | Action |
|---|---|---|---|
High-TVL stablecoin pairs (e.g., USDC/USDT) | Low extraction; tight spreads and low volatility make JIT unprofitable relative to gas costs | Passive LPs, yield aggregators | Monitor for fee-tier changes that could alter profitability; low priority for JIT-specific mitigation |
Mid-TVL bluechip pairs (e.g., ETH/USDC at 5bps) | Moderate extraction; JIT bots target larger swaps where fee capture exceeds gas and priority fee costs | Active and passive LPs, DEX aggregators | Compare realized LP returns against JIT-adjusted benchmarks; assess whether 5bps tier remains viable for passive positions |
Low-TVL long-tail pairs (e.g., governance tokens at 30bps) | High extraction; low liquidity depth allows JIT to capture disproportionate share of infrequent but large swaps | Passive LPs, token projects providing liquidity | Recalculate effective APR net of JIT; consider concentrated positions with narrower ranges to compete with JIT capital |
High-volatility pairs (e.g., memecoins at 100bps) | Very high extraction; volatility attracts large swap volume and wide spreads create profitable JIT windows | Retail LPs, automated vaults | Assume passive returns are significantly below quoted APR; evaluate whether active management or hook-based protections are necessary |
V3 pools with wide active tick ranges | JIT bots atomically mint at exact ticks around large swaps, capturing fees that would otherwise accrue to passive positions | Passive LPs using full-range or wide-range positions | Narrow position ranges to reduce the fee slice available to JIT; monitor mempool for sandwich-bundled mint-burn patterns |
V4 pools with custom fee hooks | Extraction profile depends on hook logic; dynamic fee hooks may deter JIT by raising fees during volatile blocks | Hook developers, LP strategists | Design hooks that detect atomic mint-burn patterns and adjust fees; backtest against known JIT transaction structures |
L2 pools with low gas costs | Higher extraction; negligible gas reduces JIT breakeven threshold, making smaller swaps profitable to extract | L2-native LPs, cross-chain vault operators | Adjust return expectations downward for L2 pools; monitor JIT bot activity across Optimism, Arbitrum, and Base deployments |
Pools integrated with DEX aggregators | JIT bots monitor aggregator order flow to front-run large routed swaps, extracting fees before the swap executes | Aggregator teams, router operators | Implement private order flow submission or batch auction mechanisms to reduce mempool visibility; verify UniswapX integration status |
LP Operator Assessment Checklist
A systematic checklist for liquidity providers and risk teams to assess whether their Uniswap V3 positions are economically viable after accounting for Just-In-Time (JIT) liquidity extraction. Use this to audit existing positions, set return expectations, and identify pools where JIT extraction makes passive LPing uneconomical.
What to check: Measure the percentage of swap fees captured by JIT bots in your specific pools over a representative time window (minimum 30 days). Use Dune Analytics dashboards, EigenPhi data, or custom mempool analysis to identify atomic mint-burn patterns within single blocks.
Why it matters: JIT extraction rates of 20-40% are common in high-volume stablecoin and ETH pairs, fundamentally altering the fee revenue you can expect. A pool showing 50% APR from fees may actually deliver only 30% after JIT extraction.
Readiness signal: You have a dashboard or query that segments fee revenue into JIT-captured vs. passive-LP-captured for each pool you operate in, updated at least weekly.
Source Resources and Further Reading
Use these resources to reconstruct JIT liquidity behavior from Uniswap V3 events, pool math, and transaction ordering. Teams quantifying passive LP fee dilution should combine protocol documentation with raw block-level data rather than relying only on aggregate dashboards.
Archive Node and Trace-Based Reconstruction
A defensible JIT impact model needs archive-node access or a trusted trace provider that exposes transaction order, logs, internal calls, and block-level state transitions. Use this data to reconstruct liquidity before and after each swap, attribute fee growth to transient positions, and calculate the passive LP fee share lost to JIT liquidity. Chainscore Labs can help teams design this pipeline, test classification heuristics, and convert raw event data into pool-level LP return adjustments.
Looking to build on a specific blockchain?
We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.
EVM ecosystems
- Ethereum
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Cronos

Non-EVM ecosystems
- Solana
- Sui
- Aptos
- Hedera
- Stellar
- NEAR
Additional ecosystems
- Polkadot
- Cosmos
- TON
- Cardano
- Algorand
- Tempo
Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.
Frequently Asked Questions
Common questions from LP operators and risk teams evaluating whether JIT extraction makes specific Uniswap V3 pools uneconomical for passive liquidity provision.
The extraction rate varies significantly by pool characteristics. Research indicates JIT bots can capture 20-40% of swap fees in high-volume, low-fee-tier pools (5 bps) with moderate volatility. In stablecoin pairs with tight liquidity concentration, extraction can exceed 50% of fees that would otherwise accrue to passive LPs. Pools with higher fee tiers (30 bps, 100 bps) and lower volume see proportionally less JIT activity because the profit margin after gas costs is thinner. Teams should measure extraction rates against their specific pool's volume profile rather than relying on aggregate network averages.
Delivering blockchain solutions for 5+ years.
We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.
Selected Partners & Clients
“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”
How to get started?
If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.
Exploration & Strategy
Define your product goals and choose the right blockchain architecture for your use case.
Architecture & Design
Design the smart contracts, tokenomics, and security parameters of your system.
Development & Integration
Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.
Security & Launch
Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.
Discover our
blockchain development services.
We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.
Need a blockchain engineering team?
Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.


