Uniswap v4 hits over 90K hooks initialized and linked to deployed pools

Uniswap’s v4 architecture has now seen more than 90,000 unique hooks initialized and attached to at least one deployed pool. That number, tracked via on-chain data dashboards including Dune Analytics, represents a roughly fourfold increase from the approximately 22,600 hooks recorded earlier this year.

For a feature that didn’t exist before January 2025, that’s a steep adoption curve.

What hooks actually do

Think of hooks as plug-ins for liquidity pools. In Uniswap v4, developers can write custom smart contract logic that executes at specific points in a pool’s lifecycle: before a swap, after a swap, when liquidity is added, when it’s removed, and so on.

Before v4, if you wanted a pool to behave differently, say with dynamic fees that adjust based on volatility, you essentially needed to fork the protocol or build on top of it. Hooks let developers modify pool behavior without touching the core protocol code.

The system is also designed for gas efficiency. Hook addresses encode permission details directly in their bits, meaning the protocol can check what a hook is allowed to do without expensive storage lookups.

Uniswap v4 introduced a singleton PoolManager architecture alongside the hooks system. Instead of deploying a separate smart contract for every new pool (as in v3), all pools now live inside a single contract. This reduces deployment costs and makes it cheaper for hooks to interact with multiple pools simultaneously.

From 22K to 90K in months

The growth trajectory is notable. Early in 2026, on-chain dashboards recorded roughly 22,609 unique hook addresses that had been initialized. By mid-January 2026, that figure had climbed to approximately 89,955.

To be precise about what’s being counted: these are unique hook addresses, not total pools or total deployments. A single hook contract can theoretically be linked to multiple pools. So the 90K figure represents 90,000 distinct pieces of custom logic that developers have written, deployed, and connected to at least one live pool.

Community-maintained Dune dashboards, supported by both Uniswap Labs and independent contributors, have made this data publicly accessible.

Notable hooks in the wild

Not all hooks are created equal, and a few stand out. DualPool, developed in partnership with Spark, is an audited and open-sourced hook designed to generate yield on idle liquidity sitting in pools. The core insight is straightforward: most liquidity in a concentrated liquidity pool isn’t being actively used at any given moment. DualPool routes that dormant capital into yield-generating strategies until it’s needed for swaps.

Other hooks have targeted dynamic fee structures, where swap fees adjust automatically based on market conditions like volatility or trading volume. Some developers have built hooks focused on MEV-related attributes, attempting to either capture or redistribute the value that searchers and block builders typically extract from on-chain trades.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.