Uniswap v4 launched Aggregator Hooks on Oct. 22, introducing a feature that wraps external liquidity sources into standard v4 pools. The rollout already covers seven outside venues, including Curve, Fluid and PancakeSwap, across Ethereum mainnet, Base and Robinhood Chain. Uniswap said the addition gives it reach across more than 90% of DEX activity on those chains.
Uniswap’s founder also said that by embedding aggregator logic into a Uniswap v4 hook, the Uniswap API and app have become the best aggregator in the market.
For most users, the change may not feel dramatic even a week after launch. The router automatically compares prices between native pools and these wrapped pools, then selects the best path. There is no need to switch anything on manually, and no extra approval is required.
The more consequential detail is fees. Uniswap still charges fees on trades that pass through those wrapped pools, and the fees are used for UNI burns. In practice, that means Uniswap v4 can capture fees from liquidity it does not directly own. It also points to a broader shift: Uniswap is moving closer to becoming an onchain liquidity entry point, not just a venue that supplies liquidity.
From competing for liquidity to competing for routing control
Uniswap is already the largest DEX onchain, with cumulative trading volume above $10 trillion. But actual user behavior has changed as wallets and onchain liquidity aggregators have spread. Many users no longer interact with the Uniswap app directly. Uniswap remains deeply integrated into countless wallets and aggregators, so its protocol position has not weakened, but the importance of its own frontend has clearly faded.
Aggregator Hooks are meant to change that. The feature gives users deeper liquidity and better execution without changing the trading experience in any obvious way. That could help the Uniswap frontend regain some competitive ground.
Uniswap is now trying to do two things at once: remain core liquidity infrastructure while also becoming the entry point that routes trading flow. In that sense, the strategy looks closer to Jupiter’s model.
Jupiter is the most popular aggregator in the Solana ecosystem. According to DefiLlama data cited in the source, Jupiter’s cumulative routed volume has exceeded $1.3 trillion. Over the past 30 days, Solana’s total DEX aggregator volume was about $27.115 billion, with Jupiter accounting for about $13.354 billion, or nearly 49.3%, ranking first. At one point, Jupiter even controlled more than 90% of Solana aggregator volume.
Jupiter is not only an aggregator. Its own DEX posted about $2.24 billion in volume over the past 30 days, while its perpetual futures volume reached about $4.01 billion. The model is straightforward: aggregate liquidity across the Solana ecosystem, then run proprietary products in spot and derivatives alongside that traffic. The richer the external liquidity set becomes, the easier it is for the aggregator to deliver better execution. The more users enter the market through Jupiter, the more likely Jupiter’s own products are to receive that flow.
Uniswap appears to be trying to reproduce that logic in the EVM ecosystem, with one difference: it started from a position of strength in liquidity supply. By using Aggregator Hooks, Uniswap v4 can pull external protocol liquidity directly into its own routing paths, so users do not need to leave the Uniswap app. If the feature keeps improving quotes and execution, Uniswap could end up controlling both liquidity supply and traffic distribution.
Whether UNI captures more value is still an open question
For other DEXs that provide liquidity, Uniswap v4’s Aggregator Hooks are not necessarily negative. The source frames it more as a win-win setup. Those protocols can use Uniswap as an efficient distribution channel and still profit from user trading, while Uniswap extends itself from liquidity infrastructure into the routing layer.
Even so, the short-term effect on UNI value capture may be limited.
The feature has only been live for a week, and neither official dashboards nor third-party data platforms are separately tracking trades routed through Aggregator Hooks. That makes it difficult to calculate how much volume the feature has handled and how much fee revenue it has produced. Still, data compiled by crypto blogger @0xtunad around the launch offers a useful reference point.
According to that data, Uniswap v4 Aggregator Hooks completed their first trade as early as April this year. Before the public launch on Oct. 22, the system had processed 88,101 trades across three chains, with total volume reaching $2.85 billion. But 85% of that volume came from Sky’s LitePSM, meaning swaps between USDC and USDS, and Uniswap charged zero fees on those trades.
That led to a striking result. Even though Aggregator Hooks routed billions of dollars in volume over the past six months, total fees collected were only $2,059. The fee rate ranged from 0.01% to 0.10% of traded volume, and all of those funds were sent to Uniswap’s TokenJar contract.
The source says the reason Uniswap did not charge fees on Sky’s liquidity pool was likely related to joint testing, especially since the official launch date was Oct. 22. But that also brings the central issue into focus: whether Uniswap v4 Aggregator Hooks can strengthen UNI value capture depends on whether fee switches are eventually turned on for high-volume external pools.
Protocol fees collected through Aggregator Hooks are ultimately paid by users, not by the platforms being aggregated. Users may accept extra cost for convenience in lower-depth, lower-volume pools. High-volume pools are different. Fee-sensitive traders are less likely to accept added costs, and those users are often the most active traders.
If Uniswap wants to attract that group, it may avoid turning on fees for high-volume pools in the early stage of Aggregator Hooks. If that is the case, the feature’s near-term effect on UNI value capture will remain limited.
