| Authors | Hayden Adams; Moody Salem; Noah Zinsmeister; Sara Reynolds; Austin Adams; Will Pote; Mark Toda; Alice Henshaw; Emily Williams; Dan Robinson |
|---|---|
| Year | 2024 |
| Project | Uniswap |
| License | Not stated in the paper |
| Official source | Uniswap v4 Core whitepaper (PDF) |
Uniswap v4 Core is a technical design paper dated August 2024. It describes a non-custodial, non-upgradeable, permissionless automated market maker for the Ethereum Virtual Machine. The paper builds on Uniswap v3’s concentrated-liquidity model and proposes optional hooks, a shared pool manager, and flash accounting to support more customizable pools and reduce some repeated deployment and token-transfer work. Uniswap announced v4 as live on January 31, 2025; that launch date is later than the paper’s publication date.
| Original paper | Original paper |
|---|---|
| Directories | Ethereum Whitepapers & Research |
What the paper changes
Earlier Uniswap versions deployed separate contracts for individual pools. V4 uses a singleton architecture: a PoolManager contract coordinates pools in a given deployment. The paper pairs this design with hooks and flash accounting. Together, these changes aim to let developers add pool-specific behavior while reducing overhead for pool creation and multi-pool operations.
Hooks: optional, pool-specific programs
A hook is an external smart contract that a pool can call at selected points in its lifecycle. Hooks are optional; a pool without one continues to use the concentrated-liquidity model. A pool can have one hook, and a hook contract can serve multiple pools. Its permissions are encoded in its address and chosen when the pool is created, so a hook cannot simply be attached or replaced after initialization.
The paper lists ten callbacks: before and after initialization; before and after adding liquidity; before and after removing liquidity; before and after a swap; and before and after a donation. Depending on its permissions and implementation, a hook can support features such as dynamic fees, limit-order-like behavior, or custom accounting. These are capabilities builders can implement, not features every pool automatically has.
Singleton and flash accounting
During a PoolManager lock, v4 tracks net token changes as deltas and settles them before the lock ends. This can avoid sending tokens between separate pool contracts after every intermediate step, which is useful for multi-hop trades and composed operations. The design uses EIP-1153 transient storage for temporary transaction data. “Flash accounting” describes this settlement model; it does not mean an account can leave a trade with an unpaid balance.
Native ETH and custom accounting
V4 supports native ETH pairs alongside wrapped ETH. The paper also describes custom accounting: hooks can return deltas that alter how a swap or liquidity operation is accounted for. This can extend the built-in concentrated-liquidity behavior or, in some designs, bypass it in favor of a custom curve. Such flexibility also means pools can behave differently even when they share the same PoolManager.
ERC-6909, fees, and donations
The paper describes ERC-6909 claims for keeping token balances within the singleton, which can reduce repeated transfers for some workflows. It also discusses dynamic swap fees, a capped governance fee mechanism, and donate(), which can direct either or both pool tokens to in-range liquidity providers. The precise behavior depends on the pool configuration, hook permissions, and deployed code.
Limits and risks
- A hook is custom code. Its permissions, source, admin controls, external calls, token dependencies, and settlement logic need to be reviewed for the specific pool.
- The hook address and permissions are fixed when the pool is initialized. A different hook generally means a different pool.
- Uniswap’s developer documentation cautions that creating a hook does not guarantee that the Uniswap frontend will route liquidity or trades through that hook.
- The whitepaper is a technical design document, not a security guarantee. The paper’s disclaimer does not state a software license; do not infer the license for the codebase from the paper.
Check the exact pool key, hook address, token contracts, liquidity, fee settings, and any upgrade or administrative controls before interacting. A hookless pool and a pool using custom accounting can have materially different risk surfaces.
Launch context
The paper is dated August 2024. Uniswap Labs announced the protocol as live on January 31, 2025, initially across several networks. Network support, routing, and available liquidity can change, so consult current deployment information before assuming a particular chain or pool is available.
Social Media Sentiment
A small sample of Reddit discussion is mixed and mostly technical. A recent r/defi thread treats v4 as a programmable pool platform while emphasizing that each hook can create a distinct risk profile; commenters also debate whether added complexity earns its keep. An r/Uniswap discussion asks for a reliable directory of safer hooks. These are anecdotal, low-engagement conversations, not a representative survey or a safety assessment of any particular hook.
Last updated: 2026-10
Related Terms
See Also
Sources
- Adams, Hayden; Salem, Moody; Zinsmeister, Noah; Reynolds, Sara; Adams, Austin; Pote, Will; Toda, Mark; Henshaw, Alice; Williams, Emily; and Robinson, Dan. (2024). Uniswap v4 Core. Official paper (PDF).
- Uniswap Developers. Uniswap v4 Hooks. Developer documentation on optional, pool-specific hooks and their callbacks.
- Uniswap Labs. (2025, January 31). Uniswap v4 Is Here. Launch announcement.
- Ethereum Improvement Proposals. EIP-1153: Transient Storage Opcodes. Specification referenced by the paper.
- r/defi. (2026, September). Uniswap v4 is a pool platform, not a single risk profile: How are you evaluating hooks? Discussion of hook-specific evaluation and risk.
- r/Uniswap. (2025, February). Uniswap v4 Hook Library. Question about finding and evaluating hooks.