
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 u
Connect your wallet to join the discussion.
No comments yet. Be the first to share your take.
Claim + evidence
Interpretations post onchain directly. Prediction stakes happen separately below.
ID: proposal:uniswap:0x65503933c85b5c813a350603a6f4be143e911f073ae17ff109aa978f494ae4bc
Cast your interpretation on this proposal via MO
Voting contract not deployed on this network