Uniswap adds outside liquidity to its router, ties fees to UNI burns
DeFi & Yields ·
A new v4 hook lets Uniswap's web app pull quotes from seven outside liquidity sources on three chains, folding them into the same swap flow used for its own pools.
Uniswap turned on Aggregator Hooks on October 22, 2026, across Ethereum mainnet, Base and Robinhood Chain, according to defiprime.com. The feature is live in both the web app and the API, and it works by presenting external liquidity venues as standard Uniswap v4 pools, so the existing router logic can reach them without any separate integration path. Uniswap states that seven sources are available at launch and that they cover more than 90% of DEX activity on the three supported chains, though the company has not named those sources or specified the period over which that coverage figure was measured, a detail also noted by theblock.co.
The mechanism works without extra steps for traders. External venues are included automatically in web app routing, with no option needed to select an outside source and no new approvals required. The router refreshes quotes from connected sources every block and assembles a route spanning Uniswap pools and external liquidity, with the entire trade executing in one transaction.
The economic hook is in the fee layer. Swaps that touch these wrapped external sources still pay protocol fees that feed into UNI burns, meaning liquidity sitting outside Uniswap can now generate burn-contributing revenue whenever a trade is routed through it. Uniswap has not disclosed a fee rate, expected revenue, or a projected burn figure tied to the expansion, so the scale of the effect at launch cannot be quantified from the announcement.
Underlying adapters are built to preserve how each external venue already behaves. A Curve pool holding eight tokens, for instance, can surface as 28 separate v4 pools while sharing a single hook address, letting routers detect when distinct trading pairs actually draw on the same underlying reserves. Fluid uses a comparable one-hook-per-pool design, including collateral-and-debt and concentrated-liquidity implementations, though the concentrated-liquidity version is still listed as pending for mainnet. A separate adapter for v2-style pools uses one shared deployment with an immutable factory to resolve each external pair.
What remains unconfirmed is which seven sources are actually active on each chain, what fee configuration is deployed, and when Uniswap will expand the list of supported chains or sources, since no timeline has been given for either.