Uniswap v4 hooks and the impermanent loss problem

An automated market maker prices trades against pooled inventory. When the price of one asset in a pool rises, arbitrageurs buy it from the pool until the pool’s price matches the market, and the pool ends up holding less of the asset that rose and more of the one that fell. The provider who supplied that inventory has, in effect, sold the winner and bought the loser on the way. The gap between what the position is worth and what simply holding the two assets would have been worth is impermanent loss, and it becomes permanent on withdrawal.

How bad is it

Worse than most participants assume. A widely cited study by Bancor and IntoTheBlock of Uniswap v3 liquidity providers in volatile pairs found that more than half were unprofitable once impermanent loss was set against the fees they earned. Concentrated liquidity, which lets a provider deploy capital inside a chosen price range, increases fee capture but also increases divergence loss when price moves, and turns liquidity provision into an active strategy that must be managed.

What v4 changes

Uniswap v4 launched on Ethereum mainnet in January 2026 with simultaneous deployments on several rollups. It keeps concentrated liquidity and adds three things: a single contract that holds every pool, flash accounting that nets balances at the end of a transaction, and hooks, which let a pool’s creator attach custom logic to swaps and liquidity events. Hooks are the part that matters for impermanent loss. A pool can now charge a fee that rises with volatility, so that providers are paid more in exactly the conditions that cost them most. It can rebalance positions automatically, hedge them in a perpetuals market, or capture some of the value that arbitrageurs previously took.

• Dynamic fees that scale with realized volatility instead of a fixed tier
• Automated range rebalancing according to a rule the pool encodes
• Hedging hooks that offset directional exposure in derivatives markets
• Mechanisms that return part of arbitrage value to liquidity providers

The Solana version

The same idea arrived on Solana earlier in a different form. Meteora’s dynamic liquidity market maker organizes liquidity into discrete price bins and raises fees automatically when volatility rises, with the explicit aim of compensating providers for divergence risk during the periods that create it. The design choice, volatility-linked fees, is the same one that v4 hooks make available on Ethereum, which suggests the market has converged on where the problem lies.

Does it work

Partly, and with new risks. Higher fees in volatile periods offset divergence loss; they do not eliminate it, and in a large one-directional move no fee schedule keeps pace. Automated rebalancing crystallizes loss on each rebalance and can be exploited if its rule is predictable. Hooks are arbitrary code attached to a pool: Trail of Bits’ 2026 guidance on building secure hooks catalogs the ways a badly written hook can drain a pool or lock liquidity, and a provider now has to diligence the hook as well as the protocol. The honest summary is that the tools to manage impermanent loss have improved considerably, and the discipline required to use them has increased in proportion.