Uniswap launched Aggregator Hooks on October 22, 2026, making external liquidity available through its web app and API on Ethereum mainnet, Base and Robinhood Chain. The launch announcement describes seven sources available initially.
TL;DR: The update lets routing software combine Uniswap pools with outside liquidity. It uses v4’s existing hook architecture to widen the choices available when constructing a swap.
How outside liquidity becomes part of a route
Uniswap says each connected source is presented to the router as a v4 pool. Quotes refresh with each block, and a selected route settles in one transaction. The company estimates that the initial sources cover more than 90% of decentralized-exchange activity on the three supported chains.
The Uniswap Labs hook documentation identifies integrations including Curve, Fluid, PancakeSwap V3 and Slipstream, alongside Uniswap v2, v3 and related forks. These adapters give routing software a common way to interact with pools that otherwise follow different designs.
For a trader, the relevant result is the final amount received after the route’s costs. A wider search can uncover a useful alternative, particularly when liquidity for a pair is spread between venues. It does not make every connected pool equally deep or every possible route economical.
Consider a swap large enough to move the price noticeably in one pool. Comparing another venue, or dividing the trade between compatible pools, may reduce that effect. For a small swap, the extra execution cost of a complicated route could outweigh a marginally better quoted price.
What hooks change for developers
The protocol’s v4 hook documentation describes hooks as external contracts attached to individual pools. They can run logic around actions such as swaps and liquidity changes. A pool can have one hook, while the same hook can serve multiple pools.
The hook is selected when a pool is created. Selecting a different hook requires creating a new pool; an existing pool’s attachment cannot be replaced. That makes the pool’s identity and behaviour meaningful to software integrating with it.
The documentation also warns that creating a hook does not automatically secure routing through Uniswap’s front end. That distinction matters: the protocol permits developers to build custom behaviour, while an application’s routing system decides which available opportunities it will actually consider.
Aggregator Hooks apply that flexibility to connectivity. Instead of requiring every venue to share an identical internal design, an adapter exposes a common interface. Developers still need to understand the underlying liquidity source and its execution conditions when evaluating an integration.
The launch expands the set of available routes. Whether an individual swap improves is a transaction-specific question, best answered by comparing the quoted output and execution costs for the same assets, size and moment.
Written by the News Desk and edited by Samuel Rae.
Leave a Reply