Uniswap's DualPool hook for version 4 of its protocol has completed its audit and is now ready for deployment, the team announced. The hook, which is open source, lets liquidity providers earn yield on idle assets in vaults while keeping those assets available for trading.
What the DualPool Hook Does
The hook is designed to solve a long-standing tension in automated market making: liquidity that sits idle in a pool earns nothing, but pulling it out to chase yield elsewhere means it's not there when traders need it. DualPool lets LPs deposit into vaults that generate yield, while the hook ensures the same assets remain accessible for swaps. In effect, it splits a position into a yield-bearing portion and a trading portion, both managed by the same smart contract.
This is not a new idea — several projects have tried variations — but Uniswap's implementation is notable because it's built directly into the v4 hook architecture. That means it can be deployed by anyone without needing to fork the core protocol.
Audit and Open Source Release
The code has been audited by an external firm, though the team did not name the auditor in the announcement. The audit report is public, and the hook's source code is available on GitHub under an open-source license. That transparency allows other developers to inspect the logic, suggest improvements, or fork it for their own use.
Uniswap v4 itself is still in development, but hooks like DualPool are being prepared ahead of the mainnet launch. The team said the hook is ready for deployment once v4 goes live.
For LPs, the hook offers a way to earn additional returns without sacrificing liquidity. Instead of leaving tokens idle in a pool, they can deposit into a vault that generates yield — say, from lending protocols or liquid staking — while the hook ensures the tokens can still be used for swaps. The yield earned is on top of the usual trading fees.
The catch is that the vault must be compatible with the hook's logic, and LPs need to trust the vault's smart contracts. The team recommends using only audited vaults and notes that the hook itself does not manage the vault's risk.
Deployment is expected in the coming weeks, pending final checks. The team said they will share a specific date once the v4 mainnet launch is confirmed.
