News
Uniswap (UNI) says aggregator hooks are live in its Web App and API, routing external liquidity through v4 pools across three chains.
Uniswap (UNI) said on October 22, 2026 that aggregator hooks are now live in its Web App and API, giving v4 the ability to wrap external liquidity sources and treat them as pools on Ethereum mainnet, Base and Robinhood Chain. The launch matters because it extends Uniswap’s routing beyond native v4 liquidity and, according to the company, can direct swap activity through external venues while still settling in a single transaction.
Evidence and context
In its announcement, Uniswap said seven sources are available at launch and that they cover more than 90% of DEX activity on the three supported chains. The company also said Uniswap v4 is already the largest decentralized exchange by volume, with more than $4.5 trillion swapped. Those figures were provided by Uniswap in the Oct. 22 post and were not independently verified in the source material.
Uniswap described aggregator hooks as smart-contract wrappers that turn external liquidity sources into v4 pools, allowing routers to pull fresh quotes every block and assemble the most efficient route from both native pools and outside sources. The company said swaps routed through these pools pay protocol fees that contribute to UNI burn, linking the feature to its broader protocol-fee design. A related governance post on July 7, 2026 proposed a fee framework that included aggregator-hook pools, but that publication established the proposal rather than later execution.
Separate background material published by Uniswap Labs and cited in the supplied context shows that routing documentation on Oct. 22, 2026 listed a Tempo aggregator hook as an available source of external onchain liquidity. That documentation update supports the availability of at least one integration, but it does not establish support for every external venue or hook. The same context notes that integration standards remained a design issue in the June 30, 2026 URC-4 discussion, which proposed interfaces for indicative quotes, liveness, gas budgeting and price-bounded simulation.
The launch also arrives against critical commentary from Ekubo, which on Aug. 6, 2026 argued that aggregation belongs in routers rather than hooks because of execution overhead and integration complexity. That view represents a competing protocol author’s assessment, not an independently verified benchmark. The supplied material does not include performance data showing whether aggregator hooks reduce gas costs or improve execution relative to other routing architectures.
