Uniswap v4 aggregator hooks go live, routing seven external DEXs

Uniswap Labs has launched aggregator hooks on Ethereum mainnet, Base and Robinhood Chain, exposing seven external liquidity sources as if they were native Uniswap v4 pools. The feature is live in both the Uniswap Web App and the API, per Uniswap's own launch post and The Block.

The first aggregator hook went live on Tempo in March 2026; today's launch is the production rollout across the three main deployment chains.

How the mechanism works

Aggregator hooks are the mechanism promised in the UNIfication proposal first circulated in November 2025. Each hook wraps a non-Uniswap pool in a v4 interface, per Uniswap Labs:

• The router sees the external pool as a Uniswap v4 pool. Same quote path, same approval path, same settlement flow.
• Routers pull fresh quotes from each connected source every block, so stale pricing doesn't poison a route.
• A single swap can mix Uniswap pools and external sources in one transaction, with no new token approvals.
• Trades that route through an aggregator hook pay Uniswap protocol fees, and those fees feed the UNI burn mechanism.

The Block names Fluid, Curve and PancakeSwap as among the seven external sources connected at launch; the Uniswap post does not enumerate the full list.

Why this changes the DEX routing stack

Until today, routing on-chain between Uniswap and an external pool required a separate aggregator (1inch, 0x, Odos, Matcha) and typically two approvals, two signatures, or an off-chain quote. The aggregator-hook pattern collapses the routing stack:

• A user who swaps on app.uniswap.org now implicitly uses an aggregator that routes to Uniswap and the seven external venues in one call.
• An integrator calling the Uniswap API gets the same multi-source behaviour without integrating 1inch or 0x separately.
• The external source still earns LP fees; the router captures the surplus between the two legs.

Uniswap Labs claims the seven sources cover more than 90% of DEX activity on the three launch chains.

Fee and UNI mechanics

Three facts matter for the UNI token economy:

1. External-routed swaps do pay Uniswap protocol fees, per the launch post.
2. Protocol fees feed the UNI burn mechanism proposed under UNIfication.
3. External LPs earn their native pool fees unchanged; the fee accrual to Uniswap is on top.

The launch post gives no fee percentage, and does not disclose the split between the external pool's fee and the Uniswap protocol fee on a routed trade.

What to watch

1. The seven source list. Fluid, Curve and PancakeSwap are three. The other four will matter for whether Robinhood Chain's launch depth is anchored by existing CEX-adjacent flows (PancakeSwap, Binance-adjacent liquidity) or by DeFi-native pools.
2. Whether external DEXs push back. A router that treats a Curve pool as a Uniswap v4 pool captures the fee surplus. Curve, PancakeSwap and others may price their liquidity differently once Uniswap's web app routes volume through them.
3. The burn delta. The UNI burn depends on actual routed volume through hooks, not announcement coverage. The Dune v4 trade-count dashboards will show it within days.

Context

Aggregator hooks are the second major piece of the UNIfication plan to ship, after the fee switch work earlier in 2026. The pattern — a DEX that captures external liquidity as part of its own router without the external venue's cooperation — mirrors the move Aerodrome and Velodrome's merge into Aero made at the chain level. Both signal the same shift: DEX teams are consolidating liquidity surfaces rather than growing new ones.

The move also lands against Robinhood Chain, which Uniswap says now carries roughly $12.8 billion of monthly volume routed through v2, v3 and v4. Aggregator hooks make that surface the deepest non-Ethereum home for Uniswap routing.