This proposal is part of the protocol fee rollout, following proposals #93, #94, #95, #96, #99, #100, and #102. It uses the expedited governance process approved in UNIfication, where fee parameter update proposals can bypass the RFC stage and go directly to a five-day Snapshot followed by an onchain vote.
v4 protocol fees went live in July, and v4 now accounts for roughly half of Uniswap volume. Much of that growth comes from hooks, which let builders launch new pools with custom behavior. Hooks are very diverse: some use static LP fees, some use dynamic fees, and some use custom accounting to govern swap behavior.
The initial protocol fee controller for V4 doesn’t have the expressivity required to deal with all the different types of hooks popping up in the ecosystem. This proposal upgrades the v4 fee logic so governance can set fees for any hook through flexible and reusable rules. The upgraded logic also gives hooks a direct way to opt into the protocol fee themselves and set appropriate fees for their pools.
Specifically, this proposal:
- Replaces the
V4FeePolicyof theV4FeeAdapteron all eight chains where v4 protocol fees are live - Keeps fee levels unchanged for every pool currently paying the v4 protocol fee
- Opts in pools using Uniswap Labs-owned hooks, and does not enable fees on pools using third-party hooks
Note there is an additional snapshot running in parallel to activate v4 protocol fees under this same framework on Celo, Soneium, X Layer, World Chain, and Zora.
Implementation Details
The upgraded policy removes families in favor of hook rulesets: contracts that return a protocol fee for a given pool through a shared getProtocolFee(PoolKey) interface. Governance assigns rulesets, and the adapter resolves each pool’s fee by checking the following in order:
- Pool override. If governance has set a fee for the specific pool, that fee applies.
- Hookless pool. If the pool has no hook, the ruleset registered for hookless pools applies. If none is set, the global default fee applies.
- Governance-assigned Ruleset. If governance has assigned a ruleset to the pool’s hook, that ruleset applies.
- Hooked static fee pool. If the pool has a hook but uses a static LP fee without custom accounting, the ruleset registered for hooked static fee pools applies. If none is set, resolution continues.
- Hook opt-in. If the hook declares support for the ruleset interface (ERC165) and implements
getProtocolFee(PoolKey), that value applies. If the hook doesn’t declare it, resolution continues. - Global default. Otherwise, the global default set by governance applies. The global default is set to 0 in this proposal.
If a ruleset or opted-in hook reverts, the fee update for that pool fails and the pool keeps its current protocol fee.
Hook opt-in. Hooks do not register with the fee controller directly; instead, any hook can opt into the protocol fee by implementing getProtocolFee(PoolKey) and declaring support for the ruleset interface (ERC165). The simplest path for most hooks is to compute an effective LP fee and pass it to the hookless fee curve, which the hookless ruleset exposes for this purpose. Hooks that look up the hookless ruleset through the adapter automatically follow any future change governance makes to it.
Governance-published rulesets. Governance can publish a shared fee ruleset for a type of hook. Any hook of that type can opt in by pointing to its reserved key, and when governance updates the ruleset, every hook using it updates automatically. Aggregator hooks will be the first to use this. We are also implementing rulesets for the StablePair and VolatilePair hook.
Batching. Hook-to-ruleset assignments and fee pushes accept multiple hooks or pools in one call.
Unchanged. Permissionless fee pushing, TokenJar functions, ownership and other existing fee controller mechanics remain as they are today.
For Hook Developers
Hooks opt into the protocol fee by implementing getProtocolFee(PoolKey), which returns the protocol fee for that pool, and declaring support for the ruleset interface (ERC165). Hooks do not need to register with the fee adapter. There are three ways to implement it:
- Use the hookless fee curve. Compute your pool’s effective LP fee and pass it to the hookless ruleset’s curve function. For hooks that charge an extra fee through custom accounting, the effective LP fee is the static LP fee plus that extra amount. Look up the hookless ruleset through the fee adapter rather than hardcoding its address, so your hook follows any future change governance makes to the curve.
- Use a governance-published ruleset. Look up the ruleset registered under your hook type’s reserved key (for example, the aggregator key) and forward the call to it. If governance later changes that ruleset, your hook picks up the change with no action on your part.
- Return your own value. Return any fee directly, including 0. A hook that returns 0 has opted in at a zero fee, but Governance can override this via assignment if it chooses.
If getProtocolFee(PoolKey) reverts, the fee update for that pool fails and the pool keeps its current protocol fee. Governance can also set a fee for any pool, or assign a ruleset to any hook, directly through a vote. Either one takes priority over the hook’s own value.
Initial Configuration
| Pool category | Configuration at activation |
|---|---|
| Hookless pools | Static fee curve from the v4 activation temp check, registered as the hookless ruleset |
| Aggregator hook pools | Aggregator ruleset at current levels: 10bp for volatile pairs and 3bp select stable pairs; on Base, 3bp and 1bp respectively |
| StablePair and VolatilePair hooks | Governance-assigned StablePair and VolatilePair hook rulesets, which charge each pool the fee of the equivalent hookless pool |
| Hooked static fee pools | No ruleset set |
| Pools using third-party hooks | No fee unless the hook opts in |
| Global default | 0 |
Proposal Spec
Pre-proposal (to be completed by Uniswap Labs prior to the onchain vote)
- Deploy the upgraded
V4FeePolicyand its ruleset contracts on Ethereum, Arbitrum, Base, OP Mainnet, BNB Chain, Polygon, Robinhood Chain, and Arc - Configure each deployment as described in Initial Configuration above, with ownership verified against the governance-owned executor on each chain
This post will be updated shortly with addresses and explorer links once deployed.
In this proposal (executed if the vote passes)
The proposal executes eight actions, one per chain, each delivered through that chain’s existing governance path:
// Ethereum (Timelock)
V4_FEE_ADAPTER.setPolicy(NEW_V4_FEE_POLICY)
// Arbitrum, Robinhood Chain (retryable ticket to the aliased Timelock)
INBOX.createRetryableTicket(...) encoding
V4_FEE_ADAPTER.setPolicy(NEW_V4_FEE_POLICY)
// Base, OP Mainnet (L1CrossDomainMessenger to CrossChainAccount)
L1_CROSS_DOMAIN_MESSENGER.sendMessage(CROSS_CHAIN_ACCOUNT, ...) encoding
V4_FEE_ADAPTER.setPolicy(NEW_V4_FEE_POLICY)
// BNB Chain, Arc (Wormhole)
WORMHOLE_SENDER.sendMessage(targets, values, datas, UNISWAP_WORMHOLE_RECEIVER, WORMHOLE_CHAIN_ID) encoding
V4_FEE_ADAPTER.setPolicy(NEW_V4_FEE_POLICY)
// Polygon (FxRoot)
POLYGON_FX_ROOT.sendMessageToChild(ETHEREUM_PROXY, abi.encode(targets, datas, values)) encoding
V4_FEE_ADAPTER.setPolicy(NEW_V4_FEE_POLICY)
Once executed, the new policy’s fees are pushed to active pools through the permissionless batch update.
RELEVANT ADDRESSES:
| Name | Network | Address | Description |
|---|---|---|---|
| V4_POOL_MANAGER | Ethereum | 0x000000000004444c5dc75cB358380D2e3dE08A90 | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | Arbitrum | 0x360e68faccca8ca495c1b759fd9eee466db9fb32 | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | Base | 0x498581ff718922c3f8e6a244956af099b2652b2b | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | OP Mainnet | 0x9a13f98cb987694c9f086b1f5eb990eea8264ec3 | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | BNB Chain | 0x28e2ea090877bf75740558f6bfb36a5ffee9e9df | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | Polygon | 0x67366782805870060151383f4bbff9dab53e5cd6 | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | Robinhood Chain | 0x8366a39cc670b4001a1121b8f6a443a643e40951 | Uniswap V4 Pool Manager |
| V4_POOL_MANAGER | Arc | 0x8366a39CC670B4001A1121B8F6A443A643e40951 | Uniswap V4 Pool Manager |
| V4_FEE_ADAPTER | Ethereum | 0x89A5D5bF00a27D55c02951E49078a5C5771051dB | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | Arbitrum | 0x6b3C04567CC62fc5D6AB8D50f1bc1Dee161eb2Cc | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | Base | 0xc53DD825dedBE7814562528A1A30e8e5BCbB4b55 | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | OP Mainnet | 0xd85393784234fB2ee4f077867A8B78E1aD4cE56B | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | BNB Chain | 0x66276D2e80784180E4B9b859e4327b9C5646B87c | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | Polygon | 0x59e84309Afa65F084F9c03668583d231afB12cc6 | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | Robinhood Chain | 0x6d0009504D129CF5002Dba61D9Ae8575AA79314c | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| V4_FEE_ADAPTER | Arc | 0x2f2bd3F43880b9644211f16d861b0672aaB23782 | Existing Uniswap V4 Fee Adapter (protocol fee controller) |
| NEW_V4_FEE_POLICY | All eight chains | TBD | Upgraded Uniswap V4 Fee policy |
| HOOKLESS_RULESET | All eight chains | TBD | Static fee curve ruleset |
| AGGREGATOR_RULESET | All eight chains | TBD | Aggregator hook ruleset |
| STABLE_PAIR_HOOK_RULESET | All eight chains | TBD | StablePair hook ruleset |
| VOLATILE_PAIR_HOOK_RULESET | All eight chains | TBD | VolatilePair hook ruleset |
Next Steps / Timeline
- Snapshot: Nov 16 - Nov 21, 2026
- Onchain vote: Following a successful Snapshot
A companion proposal activates v4 fees with this adapter on Celo, Soneium, X Layer, World Chain, and Zora.