What happened
Uniswap v4 has passed 90,000 hooks initialized and tied to deployed pools, according to a CryptoBriefing report Friday citing on-chain telemetry. Hooks are the defining feature of v4: contracts that plug into a pool's lifecycle at defined points, before or after a swap, on liquidity add or remove, at initialization, and change how the pool behaves without forking the protocol. Uniswap Labs shipped v4 to mainnet in mid-2025 on the back of a singleton architecture that collapses every pool into one contract, cutting deployment gas and enabling hook composition that wasn't practical in v3.
The 90,000 figure counts hook instances wired to live pools, not unique hook contract designs, so the raw number overstates diversity. It still marks the point where hooks moved from a developer curiosity to a default building block. For context, v3 spent its first year growing pool count, not pool logic.
v4 is doing both at once.
Why it matters
AMMs have been stuck for two years. Concentrated liquidity fixed capital efficiency in 2021 and nothing structural has landed since. Hooks are the first credible attempt to make an AMM programmable at the pool layer rather than the router layer.
That distinction matters. Router-level logic, the kind 1inch and CoW Swap built businesses on, sits outside the pool and can't touch state during a swap. Hook logic runs inside the pool's execution, which is where dynamic fees, on-chain limit orders, MEV internalization, and LP-native yield strategies actually need to live.
Ninety thousand deployed instances tells you builders are shipping, not just prototyping. The composition also matters. A pool can chain hooks for dynamic fees plus a TWAMM plus a KYC gate, which is the kind of stack a traditional venue would need a whole new protocol to express.