Skip to content
Blockchain Posts

governance

Uniswap v4 protocol-fee temp check clears at ~93%, binding on-chain vote follows

Uniswap Labs' Snapshot temperature check on activating v4 protocol fees closed July 12, 2026, with roughly 93% support. Binding on-chain vote runs the week of July 13.

by 6 min read
governanceuniswapdefiethereumprotocol

The Snapshot temperature check on activating Uniswap v4 protocol fees closed on July 12, 2026, with roughly 93% support for the "Yes" option. The temp check was posted by Uniswap Labs on the governance forum at gov.uniswap.org — [Temp Check] Activate v4 Protocol Fees and ran from July 7 through July 12. A binding on-chain governance vote follows during the week of July 13. The proposal extends the existing UNIfication buyback-and-burn program — posted to the Uniswap governance forum in November 2025 and passed on-chain in December 2025 — from v2 and v3 revenue to a first slice of Uniswap v4.

What the proposal actually does

UNIfication routes protocol-fee revenue into per-asset TokenJar contracts that buy UNI on the open market and burn it. The mechanism is already live across the eleven chains where the earlier UNIfication vote activated fees on v2 and v3 pools.

The v4 extension adds three families of v4 pools to the same plumbing:

  • v4 pools without hooks — vanilla concentrated-liquidity pools that mirror the v3 model.
  • v4 pools created via auctions — pools priced through the auction mechanism.
  • v4 pools using aggregator hooks — pools whose hook contract routes flow from a registered aggregator.

Pools that use non-aggregator hooks (custom liquidity managers, curated books, permissioned strategies) are outside the scope of this proposal. The three families named above are the ones where the Uniswap protocol collects a share of the swap fee; that share is what the UNIfication contracts sweep and convert into UNI burns.

Cross-checked against secondary coverage on Cryptopolitan and Cryptonews, which describe the same three-family scope. The exact protocol-fee parameter the binding vote will encode — the share of swap fees the protocol keeps on the covered pools — is the audit-trail number to check on the executor transaction after the on-chain vote settles.

Governance timing

Uniswap governance runs fee-parameter changes on a compressed path: the RFC step is skipped, the temperature check on Snapshot precedes a binding on-chain vote on Uniswap's Governor Bravo, and if the on-chain vote passes it queues in the timelock before an executor transaction encodes the change. The path is documented in the UNIfication forum post that preceded the December 2025 vote.

The temperature check itself is non-binding — a Snapshot gasless poll that measures sentiment, not a treasury or contract action. But the ~93% margin means Uniswap Labs went into the on-chain vote with de facto delegate alignment on the "Yes" side.

Numbers block

Proposal type          : v4 protocol-fee activation extension of UNIfication
Governance forum       : gov.uniswap.org/t/temp-check-activate-v4-protocol-fees/26162
Temperature check      : Snapshot, July 7 – July 12, 2026
Result                 : ~93 % For (secondary sources; forum thread refs)
Binding on-chain vote  : week of July 13, 2026 (Governor Bravo)
Pool families covered  : (1) v4 pools without hooks
                         (2) v4 pools created via auctions
                         (3) v4 pools using aggregator hooks
Excluded               : v4 pools with non-aggregator hooks
UNIfication scope now  : 11 chains, v2 + v3 pools; extension adds v4 slice
Mechanism              : protocol fee → per-asset TokenJar contracts
                         → UNI open-market buyback → burn
Predecessor vote       : UNIfication, on-chain passed Dec 2025
                         (Uniswap Agora proposal #93)

Figures cited by Uniswap Labs on the forum and cross-verified against Cryptopolitan, Cryptonews, and the UNIfication Agora proposal page.

What v4 revenue looks like

Uniswap v4 launched in January 2025 and has climbed steadily; the DefiLlama v4 dashboard tracks TVL, fees and volume across chains. Until this proposal executes, v4's protocol-fee slot on the three named families has been held at zero — pools accumulate LP fees, but no protocol share has been routed anywhere pending governance. The extension flips the toggle on for those families and pipes the resulting fee stream into the same UNI-burn contracts UNIfication already runs on v2 and v3.

Attribution — read carefully

Two claims travelling through secondary coverage need a hedge:

  • The ~93% support figure. Snapshot temperature-check pages show For / Against totals in UNI-weight terms; the 93% number comes from multiple secondary write-ups summarising the pane. Treat as directional until the on-chain vote provides the delegate-weighted signal.
  • The three families included in scope. The forum post names them; secondary write-ups repeat them. The exact list of live pools captured in each family — especially the aggregator-hook family, where inclusion is opt-in via a registered aggregator address — is the operational detail readers should check on the executor transaction once the binding vote closes.

Neither claim is disputed across sources; the caveats above are about where the number is verifiable, not whether it is contested.

What to watch

  1. The binding on-chain vote outcome and the executor tx. The vote runs the week of July 13. If it clears the 40M-UNI quorum, the executor transaction on Ethereum mainnet is the audit-trail moment — it encodes the fee-take parameter into the covered v4 pool families and turns fee accrual on.
  2. Which v4 pools the fee-take actually captures on day one. The proposal names the three families by category. The set of live pools in each family — especially aggregator-hook pools, since aggregator status is opt-in — is the operational question. Expect a TVL / fees table from Uniswap Labs at execution, and validate against DefiLlama v4.
  3. Burn cadence. UNIfication converts fees to UNI via open-market buys, not a permit-based direct swap. The burn cadence and average buyback slippage on the v4 slice will follow the same TokenJar rhythm as the v2/v3 sweeps. Watch the TokenJar contract addresses on Etherscan for the first post-vote sweep.
  4. Robinhood Chain protocol-fee expansion. A parallel temperature check on activating Uniswap protocol fees on Robinhood Chain is live on the governance forum — the L2 launched July 1, 2026 on Arbitrum Orbit with Chainlink infrastructure. If both extensions pass, UNIfication starts sweeping v4 pool revenue and a share of the Uniswap deployment on Robinhood Chain in the same governance window.

Context — the sequenced expansion of UNIfication

The original UNIfication proposal, posted to the forum in November 2025 and ratified on-chain in December 2025, was the switch from "the fee is off" to "the fee is on across v2 + v3." The v4 extension is not a new mechanism — it is a scope enlargement of a mechanism already burning UNI. Every three-to-six months since UNIfication passed, a follow-up temperature check has enlarged the perimeter: more chains, more pool families, and now the v4 versioning.

Two things flow from the pattern. First, delegate participation has stayed high across the follow-ups; the ~93% margin here is consistent with the December on-chain vote (which crossed 125M UNI For against negligible Against). Second, the Uniswap Foundation is running the parameter cadence in small, low-controversy increments — protocol-fee toggles on specific pool families, chain by chain — rather than one omnibus vote. That deliberate pace is what has kept the delegate base aligned across each successive UNIfication extension since Q4 2025.

Sources:

Related stories