How to Identify JIT Liquidity
The key to identifying JIT (Just-In-Time) liquidity is to check whether there is a large liquidity injection and removal completed within the same block, occurring before and after a large trade. Such operations are typically executed by specialized bots and cannot be done manually by ordinary users.
How to Identify JIT Liquidity via On-Chain Data
Step One: Locate the Target DEX Pool
JIT liquidity mainly exists on DEXs that support concentrated liquidity, such as Uniswap V3. It is recommended to start with mainstream pools (e.g., wETH-USDC).
Completion criteria: Find the pool's contract address on a block explorer (e.g., Etherscan).
Step Two: Filter "Mint" and "Burn" Events Within the Same Block
The most distinctive feature of JIT liquidity is that within a single block, an address first performs an Add Liquidity (Mint) operation to the same pool, followed immediately by a Remove Liquidity (Burn) operation.
Key signal: Check whether there is a large Swap transaction right before or after the "Mint". The typical JIT pattern is: Mint → Swap → Burn, all happening in the same block.
Size characteristics: The amount involved in such "Mint" operations is usually extremely large. Research indicates that the minimum size of a JIT trade typically exceeds $10 million. In mainstream pools, a single JIT liquidity injection can even reach tens of millions of dollars.
Completion criteria: On the block explorer's transaction list, confirm a set of transactions that follow the "Mint - Swap - Burn" sequence and are completed within the same block.
Step Three: Analyze the Purpose (Distinguishing from Malicious Attacks)
JIT and "sandwich attacks" are structurally similar (both involve front-running and back-running), but their purposes differ. They can be distinguished by the following two points:
Impact on the trader: A JIT provider injects a large amount of liquidity before the target transaction, which reduces the slippage of that trade, benefiting the trader. In contrast, a sandwich attack manipulates prices to harm the trader's interests.
Price fluctuation: A typical sandwich attack causes the trader to execute at a price significantly deviating from the market price; in a JIT environment, the trader's actual execution price is closer to the off-chain market price.
Completion criteria: Based on slippage changes and executed prices, determine whether the "sandwich" structure reduced or increased the trader's cost.
Common Failure Reasons and Notes
Mistaking a normal "Mint-Burn" for JIT: Not every Mint and Burn within the same block is JIT. You must confirm that there is a large Swap sandwiched in between. An isolated add or remove liquidity action alone does not constitute JIT.
Ignoring JIT's impact on passive LPs: JIT "swallows" the vast majority of fees from that particular trade, causing reduced earnings for other passive LPs in the pool. If you, as an LP, find fee earnings abnormally low, you might trace the pool's history for a high number of JIT events.
Confirmation of Completion
Successfully locating a set of transactions in a block explorer that includes the "Mint → Swap → Burn" sequence within the same block, and confirming that this operation helped reduce slippage for a large trade, means you have successfully identified a JIT liquidity event.
