Contents and sources 2 sections
Key points
- An extra trading interface does not turn an external pool’s reserves into additional capital.
- Quotes include a protocol-fee adjustment, subject to pool settings, direction and collection conditions.
A v4 pool interface does not create another reserve
On October 22, 2026, Uniswap Labs announced Aggregator Hooks support in its Web App and API on Ethereum mainnet, Base and Robinhood Chain. These hooks expose external liquidity through a v4 trading interface. This article examines that design; it is not a new launch announcement.[1]
The public BaseAggregatorHook is explicit: attempts to add liquidity through it revert with LiquidityNotAllowed, while swaps are delegated to each source’s _conductSwap implementation. A v4 pool identifier alone therefore does not establish that the external reserves have moved into v4.[2]
The interface defines pseudoTotalValueLocked as the amounts of the two tokens in the aggregated pool. Under that definition, a statistic that already includes the source pool’s reserves would double-count them if it added these amounts as separate capital. This is our assessment of the accounting scope, not a measurement of duplicate value on any particular website.[3]
Compare amounts after the fee adjustment
The same base contract obtains a raw quote from the external source, then adjusts for the protocol fee. For an exact-input trade, the fee reduces the output amount; for an exact-output trade, it increases the required input. Comparing unadjusted quotes can miss this cost.[2][4]
The adjustment is conditional. If the protocol fee is zero, or no nonzero TokenJar collection address is found after refreshing it, the code skips this fee adjustment. The rate comes from pool settings and a multiplier. The constructor’s 25 is a multiplier, not a 25% fee. These are behaviors of a pinned code version, not measurements of current rates on each chain.[2][4]
Our recommendation is to compare amounts after fees under the same trade conditions, then account for gas costs. Liquidity statistics also need to distinguish source-pool reserves from additional capital. Assessing a particular live pool still requires checking its deployed version and on-chain settings.[2][4]
We read the pinned source files linked below on November 7, 2026. We did not execute trades, run simulations, perform a security audit or verify deployed bytecode. Reading the code does not establish that every live pool uses the same implementation, nor does it guarantee execution prices or fund safety.
AI assisted with research, writing and translation. The cover is an AI-generated conceptual illustration. This article is not sponsored and is not investment advice.
Sources & further reading
(4)
When checking a claim, compare the source date, measurement period and conditions. Some linked pages change over time.
For information and education, not investment advice. Crypto assets are volatile. Verify independently.
