Until 2025, Uniswap v3 was a “static” fortress: the rules of the game were hardcoded. With the arrival of Uniswap v4 and the Singleton architecture, the DeFi world changed. Now each pool can have its own “soul” in the form of Hooks — smart contracts that execute at key points in the pool’s lifecycle.
For JIT bots, this marks the end of the era of easy profits. For LPs, it’s a chance to survive.
1. Hooks: The Antidote to JIT
In Uniswap v4, you can implement logic that triggers beforeModifyLiquidity (before liquidity changes) or afterSwap (after a swap). This opens up three fundamental ways to fight JIT attacks:
A. Forced Delay (Withdrawal Locks)
The simplest and most effective method. A hook can prevent liquidity from being withdrawn (Burn) in the same block in which it was added (Mint).
- How it works: If a bot can’t pull out funds instantly, it is forced to hold the position for at least 1–2 blocks.
- Result: The bot faces the risk of Impermanent Loss and market fluctuations. JIT attacks stop being risk-free.
B. Dynamic Fees
A hook can analyze volatility within a block. If there’s a sudden liquidity injection and a large swap in the current block, the hook can automatically raise the exit fee for new positions.
Little-known detail: In v4, you can implement an “anti-JIT tax” that redistributes part of the profits from short-term positions to long-term LPs.
C. Whitelisted Liquidity
Hooks allow for creating “VIP pools,” where only verified contracts or users with a certain score can supply liquidity.
2. Protection Code: Example of an Anti-JIT Hook
Below is a conceptual example of how protective logic might look in Uniswap v4 (using IPoolManager interfaces).
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;
import {BaseHook} from "v4-periphery/BaseHook.sol";
import {IPoolManager} from "v4-core/interfaces/IPoolManager.sol";
import {Hooks} from "v4-core/libraries/Hooks.sol";
contract AntiJITHook is BaseHook {
// Store the block number of the last liquidity addition for each LP
mapping(address => uint256) public lastMintBlock;
constructor(IPoolManager _poolManager) BaseHook(_poolManager) {}
function getHookPermissions() public pure override returns (Hooks.Permissions memory) {
return Hooks.Permissions({
beforeAddLiquidity: true,
afterAddLiquidity: false,
beforeRemoveLiquidity: true,
afterRemoveLiquidity: false,
beforeSwap: false,
afterSwap: false,
beforeDonate: false,
afterDonate: false,
beforeSwapReturnDelta: false,
afterSwapReturnDelta: false,
afterAddLiquidityReturnDelta: false,
afterRemoveLiquidityReturnDelta: false
});
}
function beforeAddLiquidity(address sender, ...) external override returns (bytes4) {
lastMintBlock[sender] = block.number;
return BaseHook.beforeAddLiquidity.selector;
}
function beforeRemoveLiquidity(address sender, ...) external override returns (bytes4) {
// Block withdrawals if happening in the same block as the deposit
require(lastMintBlock[sender] < block.number, "JIT Detected: Withdrawal locked until next block");
return BaseHook.beforeRemoveLiquidity.selector;
}
}
3. Forecast: Will All LPs Become Bots?
By 2026, the line between a “passive investor” and an “MEV bot” will blur completely.
- Active Management (ALM): Protocols like Gamma or Arrakis will start using JIT-like mechanics themselves to protect user yields.
- Vertical Integration: Large LPs will make direct deals with block builders so their liquidity can’t be “front-run” by JIT attacks (so-called Private Liquidity Pools).
Tip for LPs: In the v4 era, don’t just look for pools with the highest fee. Look for pools with smart hooks. Unprotected pools will be drained by bots, while pools with a 1-block withdrawal delay become safe havens for real capital.
4. MEV Ethics: Evil or Incentive?
JIT liquidity is the peak of capitalism in code. It’s harsh on lazy money, but it makes the market incredibly liquid.
- Ethical paradox: A JIT bot “steals” from LPs but gives the trader the perfect price.
- From Uniswap’s perspective — it’s a success. From the ecosystem’s perspective — it’s a challenge that pushes us to build more sophisticated financial tools.
5. Practical Survival Tips for 2026
- Stay away from “naked” pools: Avoid Uniswap v3/v4 pools without protective hooks in high-volume pairs (like USDC/WETH). There, your yield is bot food.
- Use Hook aggregators: Look for platforms that automatically rebalance your capital only into “protected” pools.
- Diversify across L2: JIT attacks are most effective on Mainnet because of Flashbots. On L2s (Base, Optimism) with fast blocks, it’s harder for JIT bots to catch opportunities, and fees are often lower, making attacks less profitable.
Cycle Conclusion
The “Predators in Pools” cycle is over. We’ve covered JIT liquidity from the first transaction to the architecture of the future. DeFi won’t get simpler — it will get faster. And now that you know how predators operate, it’s up to you: be their prey or be the one designing the rules of the game.
JIT Liquidity Mastery: The Complete Guide to MEV in Uniswap: Part 5 of 5
