Uniswap's next burn upgrade is already written into two live onchain proposals — the only thing missing is votes. With 2.94 million UNI cast and 40 million required, the July 26 close is less about sentiment than about who actually shows up to the ballot.
What Passes on July 26 — and What That 37M UNI Gap Actually Means
Two Uniswap governance proposals are in an active onchain vote window running July 19–26, 2026, and both would broaden protocol-fee collection to feed the UNI burn. As last checked, Proposal 100 ("Activate v4 Protocol Fees") and Proposal 99 ("Protocol Fee Expansion: Robinhood Chain") each showed roughly 2.94 million UNI "For," 0 "Against," and the 40 million UNI quorum not yet met — about 7.4% of the threshold needed to make either proposal executable (Proposal 100), (Proposal 99).
Quick Answer: Uniswap's July 19–26, 2026 vote on Proposals 99 and 100 would switch on v4 and Robinhood Chain protocol fees to accelerate the UNI burn. Both need a 40 million UNI quorum plus a majority; as last checked each held about 2.94 million UNI "For" — roughly 7.4% of quorum.
Sentiment is not the bottleneck — turnout is. A temperature check held July 7–12 drew 93% support, with 13.9 million UNI in favor versus about 1 million against, and the governance path was expedited past the usual request-for-comment stage (The Block). The gap between that non-binding signal and the binding 40 million quorum is a delegate-mobilization problem, not a popularity contest.
If quorum clears and a majority holds, the path to execution is mechanical:
- Timelock, then automatic execution. A mandatory roughly two-day timelock precedes automatic onchain execution across the seven chains named in Proposal 100 — Ethereum, Arbitrum, Base, BNB Chain, Polygon, Optimism and Robinhood Chain.
- Why two proposals. Uniswap's GovernorBravo contract caps each proposal at ten executable onchain actions, forcing the split and leaving remaining v4 chains for a follow-up proposal.
- If quorum fails. The proposals expire on July 26 with zero onchain effect, and resubmission restarts the governance clock — realistically six to ten weeks before another executable vote could close.
In short, the fee architecture and the burn loop are ready; the December 2025 "UNIfication" overhaul already passed with 99.9% support. What is unresolved is whether enough voting weight reaches the 40 million line before the window shuts.
The v4 Fee Architecture: V4FeePolicy, TokenJar, and the Burn Loop
The v4 fee system is a two-contract controller designed to make per-pool fees governable at scale. V4FeePolicy classifies each pool and computes its protocol fee under governance-set rules, while V4FeeAdapter enforces overrides, applies the policy fee, updates the pool, and routes collected fees into each chain's immutable TokenJar . Uniswap Labs argues this design is necessary because v4's hooks and dynamic fee tiers make manual, per-pool fee governance unworkable . The first rollout under Proposal 100 is deliberately narrow, covering only three pool families: static-fee pools without hooks, pools launched after Continuous Clearing Auctions (CCA), and aggregator-hook pools that route external venues into v4 .
Fees are set by formula, not negotiation. For static-fee and CCA pools, the protocol fee follows a curve scaled to the LP fee; for aggregator-hook pools, defaults are flat with a discount on Base and for selected stable pairs .
| Pool type | Condition | Protocol fee |
|---|---|---|
| Static-fee / CCA | 5 bp LP fee | 1.25 bp |
| Static-fee / CCA | 30 bp LP fee | 5 bp |
| Static-fee / CCA | 83.34–100 bp LP fee | 10 bp (cap) |
| Aggregator-hook | Non-Base default | 10 bp |
| Aggregator-hook | Non-Base, selected stables | 3 bp |
| Aggregator-hook | Base default | 3 bp |
| Aggregator-hook | Base, selected stables | 1 bp |
Wherever fees land, the burn loop is the same and it is structurally immutable. Fees from v2, v3, v4, UniswapX and Unichain sequencer activity route through adapters into a chain-level immutable TokenJar, where funds simply accumulate . Crucially, TokenJar balances can be withdrawn only when an equivalent value of UNI is burned through a companion "releaser," or Firepit, contract — the tokens are bridged back to Ethereum and sent to the burn address . There is no discretionary path to release fees without a matching burn; the lock-and-burn link is enforced in contract code rather than policy.
That mechanism is already live on the v2/v3 side and producing measurable results, which is what makes the v4 extension consequential. Uniswap Labs' forum figures cite roughly 7.5 million UNI (about $25.6 million) burned since December 2025, a record single-day burn near 186,000 UNI from v2/v3 fees alone last month, and monthly protocol fees rising from about $3.1 million in February to about $5.1 million in June . These are official governance figures rather than independently audited data, so treat them as context, not verified accounting. What Proposal 100 does is point v4 volume — the fastest-growing slice of Uniswap flow — into that same one-way loop.
Robinhood Chain: Why $6B in 9 Days Changes the UNI Burn Math
Robinhood Chain is the reason the July vote reads as more than housekeeping: it routes an unusually large, fast-growing pool of swap volume into Uniswap's burn loop. Robinhood launched its public mainnet on July 1, 2026, a permissionless Layer 2 built on the Arbitrum stack and aimed at tokenized real-world assets, stock tokens and agentic trading. Uniswap was a day-one partner: v2, v3, v4 and UniswapX all went live as the chain's primary public AMM at chain ID 4663, supported in the Web App, Wallet and API and quoting Robinhood Stock Tokens 24/7 through UniswapX.
The volume arrived quickly. Uniswap's Robinhood deployments took in roughly $3.1 billion in DEX volume in the first week, initially dominated by memecoins, and official Uniswap governance text says cumulative swap volume crossed $6 billion as of July 10 — nine days after launch. That trajectory, not the mechanics, is what makes supporters treat this expansion as consequential.
Two proposals connect that flow to the burn. Proposal 99 extends already-live v2 and v3 protocol-fee collection — running on eleven chains since late December 2025 — onto Robinhood Chain, so it broadens an existing model rather than inventing one. Proposal 100 adds v4 fees, with Robinhood Chain's v4 activation batched inside the seven-chain v4 rollout. Because Robinhood Chain is an Arbitrum Orbit chain, governance execution runs through retryable tickets via the chain's Inbox and the L2 alias of the Uniswap Timelock — a routing detail, but one that determines whether the fee switch actually lands onchain.
Founder Hayden Adams framed the stakes plainly.
"Given current volumes, we expect the impact on UNI burn to be substantial," — Hayden Adams, founder of Uniswap Labs, posting on X (source: The Block).
Note what he did not do: no specific figure, no formal burn forecast. That is governance framing, not a modeled projection — which is why the base and bull cases below have to reason about ranges rather than a promised number.
Base Case: Quorum Clears, v4 Fees Activate, Burn Rate Trends Higher
The base case is that both proposals clear the 40 million UNI quorum before the July 26 close and pass with their majority intact, activating v4 protocol fees on top of the running v2/v3 rollout. This is the most probable outcome, not a certainty: the July 7–12 temperature check drew 93% support, with 13.9 million UNI in favor versus roughly 1 million against , and December's UNIfication vote passed with 99.9% support — 125,342,017 UNI for, 742 against . Turnout, not sentiment, is the open variable. Closing the roughly 37-million-UNI gap depends on delegate mobilization in the final week, and the expedited path — skipping the usual request-for-comment stage — signals that large delegates are already aligned .
If quorum clears, the fee run-rate continues its established trajectory rather than spiking. Monthly protocol fees rose from about $3.1 million in February to about $5.1 million in June, per Uniswap Labs' forum figures . v4 activation adds a new fee surface on top of that existing v2/v3 base — static-fee pools, CCA pools, and aggregator-hook pools across seven chains — so the incremental burn arrives as an additive layer, not a step-change. The baseline it extends: roughly 7.5 million UNI (about $25.6 million) burned since December 2025 , with a record single-day burn of about 186,000 UNI from v2/v3 alone last month as a scale reference .
At roughly $3.50, UNI absorbs this added burn gradually over quarters . The base case is deliberately unglamorous: no near-term supply shock, but structural deflationary pressure that compounds as fee-enabled chains multiply and each v4 pool family comes online. The mechanism widens; the burn accumulates in the background. What separates this outcome from the bull case is whether Robinhood Chain volume sustains — the subject of the next section.
Bull Case: Stock-Token Volume Compounds, Burn Becomes Structurally Visible
The bull case turns on one variable: whether Robinhood Chain volume is a durable base rather than a launch spike. Uniswap's Robinhood deployments crossed $6 billion in cumulative swap volume as of July 10 , roughly nine days after Uniswap's v2/v3/v4 and UniswapX deployments went live on July 2 . Held flat, that pace extrapolates above $20 billion per month. At a blended 5 basis-point protocol fee, monthly protocol revenue from this chain alone would exceed $10 million — nearly doubling Uniswap's June run-rate of about $5.1 million, itself up from roughly $3.1 million in February .
What makes this structurally different from prior burn drivers is the volume's composition. Robinhood Stock Tokens trade 24/7 through UniswapX , creating a recurring, non-crypto-cycle demand base that is decoupled from the memecoin churn that dominated Robinhood Chain's first week of roughly $3.1 billion in DEX volume . Tokenized equities generate flow tied to traditional-market activity, not just speculative rotations — the key bull differentiator. Founder Hayden Adams argued the point directly: given current volumes, "we expect the impact on UNI burn to be substantial," he wrote on X .
The fee surface also widens beyond a single vote. Because GovernorBravo caps each proposal at ten executable actions, a follow-up Part 2/2 proposal covering the remaining v4 chains is expected after July 26 . Each additional chain compounds the fee base feeding the burn loop.
| Scenario input | Value |
|---|---|
| Robinhood Chain volume (9 days, to Jul 10) | ~$6B |
| Extrapolated monthly volume | >$20B |
| Blended protocol fee | ~5 bp |
| Implied monthly protocol revenue | >$10M |
| Current run-rate (June) | ~$5.1M |
| Illustrative monthly burn at scale (UNI ~$3.50) | >500K UNI |
Against supply, the math becomes visible. December's UNIfication already executed a retroactive burn of 100 million UNI — roughly 16% of supply — from the treasury , and about 7.5 million UNI has been burned since . With UNI near $3.50 , a sustained burn above 500,000 UNI per month against an already-reduced float marks a genuine tokenomics inflection — the difference between background accumulation and a deflation rate holders can measure quarter over quarter.
Bear Case: LP Flight, Quorum Failure, or Volume That Doesn't Stick
The bear case rests on three failure modes: liquidity providers exit frontier pools, the vote never clears quorum, or Robinhood Chain volume proves transient. Any one of them caps the burn rate near its current baseline rather than the higher trajectory supporters project. The strongest near-term risk is provider resistance, because protocol fees are extracted directly from revenue that otherwise flows entirely to LPs.
Liquidity-provider firms including Gamma Strategies oppose the v4 fee proposals, arguing that taking 10–25% of LP revenue on frontier v4 hook pools weakens liquidity where Uniswap is still competing for share against newer venues . Uniswap Labs counters that the earlier v2/v3 fee activation did not trigger major blue-chip liquidity flight . The rebuttal has a gap: v2 and v3 are mature, sticky markets, while v4 hook pools are newer and unproven under sustained fee pressure, so past resilience is a weak guide to how thin, contested pools behave once a protocol cut lands.
The second risk is that the revenue driver fails to compound. Robinhood Chain's first-week activity was heavy — roughly $3.1 billion in DEX volume — but that flow was initially dominated by memecoins . If novelty fades and stock-token adoption arrives slower than projected, the burn upside collapses back toward the pre-Robinhood baseline, and the $6 billion cumulative figure reported as of July 10 becomes a launch spike rather than a run rate .
The third risk is procedural. Each proposal must reach the 40 million UNI quorum by the July 26 close, and only about 2.94 million UNI had voted "For" when last checked . If turnout stalls, the proposals expire, v4 fees stay off, and the Robinhood Chain revenue gap persists. Resubmission would add roughly six to ten weeks and may force governance to revisit the expedited path that skipped the usual request-for-comment stage . Strong sentiment — a temperature check drew 93% support — narrows but does not eliminate the quorum risk, since favorable polling has not historically translated into guaranteed turnout on Uniswap's onchain votes.
Portfolio Implication: What UNI Holders Should Track Before the July 26 Close
The single most important signal for UNI holders before the July 26 close is the delegate "For" count on Agora, not the UNI price. A tally approaching 30–35 million UNI by July 24 suggests passage is likely, while a count stalling below 20 million by July 23 sits in high-failure territory against the 40 million quorum . When last checked, both proposals showed roughly 2.94 million UNI "For" and zero "Against," so the gap to quorum is what matters, not the lopsided direction .
The December 2025 UNIfication vote is the instructive precedent: it closed with 99.9% support and 125,342,017 UNI in favor versus 742 against . That outcome proves sentiment and delegate turnout are different variables — a 93% temperature check tells you the mood, but only delegate wallets moving their voting weight onchain clear quorum. Watch the addresses, not the ticker.
On valuation, UNI trading near $3.50 prices in modest burn expectations. Passage plus sustained Robinhood Chain volume — deployments crossed $6 billion in cumulative swaps by July 10 — could reprice the burn multiple, but the timeline runs in quarters, not the week of the vote. The mandatory ~two-day timelock before execution means even a clean pass delivers no instant fee flow.
The downside scenario has its own tracking item. If either proposal fails, monitor whether Part 2/2 — the remaining v4 chains — is bundled with a resubmission or delayed, since GovernorBravo's ten-action cap already forced this two-proposal split . That decision sets the full fee-activation timeline and the next meaningful catalyst date.
The concrete takeaway: bookmark the Agora delegate tally, mark July 23–24 as the read-out window, and treat the delegate turnout curve — not price — as the leading indicator through the July 26 close.
Frequently asked questions
What happens if the 40M UNI quorum isn't reached by July 26?
Both proposals expire with zero onchain effect. If the 40 million UNI quorum is not met by the July 26, 2026 close, v4 protocol fees do not activate and Robinhood Chain's v2/v3 fees do not switch on — the code simply never executes. When last checked, both Agora pages showed roughly 2.94 million UNI "For" against the 40 million quorum, so the gap was substantial. Resubmission is possible, but it restarts the governance clock: a fresh temperature check, an optional request-for-comment stage, a new onchain vote, and the mandatory ~two-day timelock would add roughly six to ten-plus weeks before any execution.
What is the difference between Uniswap Proposals 99 and 100?
They target different fee tracks, not different vote mechanics. Proposal 99, "Protocol Fee Expansion: Robinhood Chain," extends existing v2 and v3 protocol fees to Robinhood Chain. Proposal 100, "Activate v4 Protocol Fees (Part 1/2)," switches on v4 protocol fees across seven chains — Ethereum, Arbitrum, Base, BNB Chain, Polygon, Optimism and Robinhood Chain. The split is a technical constraint, not a strategic one: Uniswap's GovernorBravo contract caps each proposal at ten executable onchain actions, and a follow-up proposal is expected to cover the remaining v4 chains. Both proposals require the same 40 million UNI quorum and a simple majority.
How exactly does UNI get burned from protocol fees?
Protocol fees are routed through adapters into a chain-level "TokenJar," an immutable contract where fees from v2, v3, v4, UniswapX and Unichain sequencer sources accumulate. Those funds can only be released when an equivalent value of UNI is burned via a companion "Firepit"/releaser contract — that UNI is bridged back to Ethereum and sent to the burn address. Crucially, the lock-and-burn link cannot be altered by governance once deployed. The mechanism is already live: Uniswap Labs cited roughly 7.5 million UNI (about $25.6 million) burned since December 2025, including a record single-day burn of about 186,000 UNI from v2/v3 fees.
Why does Robinhood Chain matter so much for UNI's burn rate?
Volume and its character. Robinhood Chain reached $6 billion in cumulative Uniswap swap volume in its first nine days (July 1–10, 2026), with Uniswap serving as the primary public AMM on chain ID 4663. The bull case rests less on the raw figure than on the source: Robinhood Stock Tokens trade 24/7 via UniswapX, so much of the activity is tied to equity markets rather than crypto cycles. Non-cyclical protocol revenue, the argument goes, can sustain the burn rate without needing a crypto bull market. Founder Hayden Adams said on X that, given current volumes, "we expect the impact on UNI burn to be substantial."
What are the v4 protocol fee rates being voted on?
They vary by pool type. For static-fee and Continuous Clearing Auction (CCA) pools, fees follow a curve — for example, 1.25 bp at a 5 bp LP fee, 5 bp at a 30 bp LP fee, and a 10 bp cap at the 83.34 bp and 100 bp LP-fee points. For aggregator-hook pools, the default is 10 bp on chains other than Base (3 bp for selected stable pairs), while Base uses a 3 bp default and 1 bp for selected stable pairs. The initial rollout is limited to three pool families: static-fee pools without hooks, CCA-launched pools, and aggregator-hook pools that route external venues into v4.
Enjoyed this article? Subscribe to get new stories by email whenever they're published.