Uniswap after UNIfication: protocol fees, burn routing and the new governance-economics checklist

Treasury Desk Brief · Governance Economics Impact Brief

Public-source monitoring Retrieval date: 2026-06-01 Educational governance analysis only

Short executive summary

UNIfication was not just a “fee switch” proposal. The reviewed source pack frames it as a governance bundle covering protocol fees, burn routing, Unichain sequencer-fee routing, Foundation / Labs operating-model changes and a growth-budget path.

Proposal #93 executed onchain in December 2025 and included a 100M UNI transfer to 0xdead, fee-control actions and approval for a 40M UNI vesting path over two years.

Protocol-fee expansion then moved beyond mainnet: proposal #94 and proposal #95 executed in March 2026, while proposal #96 for BNB Chain, Polygon and a corrected Celo path required publication-day status treatment because the draft retrieval context and later live proposal status differed.

The burn mechanism should be read as a governance and reporting mechanism, not as a token-market thesis. Fees accumulate through TokenJar / Releaser / Firepit mechanics; the reviewed pack did not identify exact cumulative official burn totals.

This brief does not prove that UNIfication solved governance economics, that protocol fees guarantee sustainable economics, or that burn mechanics guarantee value accrual.

UNIfication in one paragraph

UNIfication, as described in the reviewed source pack, combined several governance-economics changes into one package: protocol fees and UNI burn, routing of certain Unichain sequencer fees into the same burn architecture, a retroactive treasury burn, reset of certain Labs-controlled interface / wallet / API fees to zero, Foundation-to-Labs operating-model realignment, and a growth-budget framework.

The onchain execution source for proposal #93 confirms execution status and decoded actions, including the 100M UNI transfer to 0xdead and 40M UNI approval for vesting. That makes UNIfication broader than a simple protocol-fee change. It does not prove that every planned or future component was live at the same time, nor does it provide a complete post-execution accounting report.

Protocol-fee expansion

The initial UNIfication execution applied fee logic on Ethereum mainnet. For v2, the cited Protocol Fee Configuration converts the 0.30% total pool fee into 0.25% for LPs and 0.05% for the protocol. For v3, the initial rollout targeted a curated mainnet set that the proposal described as representing 80–95% of Ethereum mainnet LP fees.

The later expansion is where delegate oversight becomes more complex. Proposal #94 executed on March 6, 2026 and covered Base, OP Mainnet, Arbitrum and mainnet fee-controller updates. Proposal #95 executed on March 7, 2026 and covered Celo, Soneium, Worldchain, X Layer and Zora. The forum source for eight more chains and remaining mainnet v3 pools explains the first post-UNIfication expansion step.

A later proposal #96 covered BNB Chain, Polygon and a corrected Celo path, with forum context in three more chains. Because the draft retrieval context and live proposal page status differed, #96 should be treated as a publication-day refresh item rather than a static claim.

Confirmed by source. Protocol-fee rollout moved from mainnet-only toward multichain execution, and post-UNIfication governance moved from a curated v3 allowlist toward a V3OpenFeeAdapter model with governance overrides possible.

What this does not prove. It does not prove uniform chain-by-chain realized fees, identical operational risk, permanent fee settings, complete public reconciliation, or that all pool-level effects are neutral. Developer docs remain useful for fee split and architecture, but later executed governance pages are stronger sources for current rollout scope.

Burn mechanism

The source pack supports two separate burn-related facts. First, proposal #93 executed a retroactive 100M UNI burn through a transfer to 0xdead. Second, the ongoing mechanism is not described as simple treasury accrual. Official protocol-fee docs describe TokenJar / Releaser / Firepit mechanics: fees accumulate, and a release flow requires UNI to be burned.

Public onchain evidence also showed Firepit release calls shortly after launch, but the reviewed pack did not find a complete official cumulative-burn series with structured totals. A Dune burn query is linked from governance materials, but exact structured values did not render in this retrieval.

Source-bound framing. The burn mechanism exists as a source-supported protocol-economics and reporting mechanism. It should not be presented as a token-market thesis, as a guarantee of value accrual, or as proof that protocol fees already produce high-quality sustainable economics.

Governance economics

Confirmed by source. UNIfication changes the accountability surface. Before UNIfication, the historic Making Protocol Fees Operational discussion focused on how to make protocol fees operational: accrual, claiming, handling fee assets and treasury destination. After UNIfication, the story becomes more complex: fee assets are routed through a burn workflow, growth work is supported through an approved UNI budget path, and Foundation / Labs responsibilities changed.

Author synthesis. Delegates now need to monitor at least five things together: fee activation status, chain-level rollout state, TokenJar / burn activity, growth-budget usage, and public reporting cadence. A slogan like “fees are on” is not enough. The governance question becomes: can delegates reconcile what was executed, where fees are active, what was burned, what was funded and what is still missing from public reporting?

For implementation context, delegates can also review Protocol Fee Deployments. The pack also notes public DefiLlama Uniswap activity metrics as monitoring context, but those dashboard values are freshness-sensitive and not equivalent to official Uniswap reporting. They can help frame accountability questions; they do not settle revenue quality, sustainability or budget adequacy.

Foundation financials / operating context

Foundation financial context is relevant, but only as governance-accountability context. The source pack says the Uniswap Foundation FY2025 Financials summary reported $49.9M in cash and stables, 15.1M UNI, 240 ETH and expected runway through January 2027 as of Dec. 31, 2025. The same source said projected spend would be updated in a Q1 2026 report after UNIfication; that post-UNIfication Q1 report was not identified in the reviewed official sources.

The pack also says official Foundation materials describe most of the Foundation team transitioning into Uniswap Labs. That supports an operating-model change, not a conclusion about token value, investment value, revenue quality or guaranteed sustainability. The Uniswap Foundation 2025 Ecosystem Update can be used as operating-context background, not as a dynamic status source unless separately archived and reviewed.

Open questions for delegates

What is the current status of proposal #96 on publication day: queued, executed or changed?
Has any #97+ fee-related proposal been posted?
Where is the official chain-by-chain reconciliation of fee activation state, TokenJar balances, burn activity and realized public revenue? The reviewed materials did not identify one.
Is there a single official cumulative burn dashboard with auditable methodology and dated totals? The reviewed materials did not identify a single official dashboard.
Where is the post-UNIfication Q1 or Q2 Foundation / Labs budget report? The reviewed materials did not identify that report.
Where is the public registry of v3 overrides, exemptions or exceptions under the open-fee model? The reviewed materials did not identify a public registry.
How can delegates compare growth-budget outflows with burn activity without turning the discussion into a token-market narrative?

Publication-day refresh checklist

Before publication, re-check:

Proposal #96 current status: queued, executed or changed.
Whether any #97+ fee-related proposal appeared.
DefiLlama Uniswap TVL / fees / revenue if any current dashboard values are quoted.
Whether official Uniswap / Foundation docs added a usable cumulative burn dashboard or official burn summary.
Whether the Dune burn query renders structured totals with a clear methodology.
Whether a post-UNIfication Q1 / Q2 Foundation or Labs budget report appeared.
Whether protocol-fee docs were updated to reflect the latest v3 / multichain scope.
Whether an official public registry of v3 overrides / exceptions exists.
If not newly confirmed, keep these as open questions rather than inferred conclusions: cumulative official burn totals, full chain-by-chain reconciliation, post-UNIfication budget report, current override registry and final status changes after the 2026-06-01 retrieval point.

What this does NOT prove

This brief does not predict UNI market behavior. It does not say UNIfication is bullish or bearish. It does not recommend voting for or against any proposal. It does not provide market-action, treasury-action or asset-use guidance. It does not prove that burn guarantees value accrual. It does not prove that protocol fees guarantee revenue quality or treasury sustainability. It does not prove that multichain rollout closes execution risk. It does not provide legal, tax, accounting or compliance conclusions. It does not prove Treasury Desk demand, WTP, PMF, traction, revenue or adoption.

Treasury Desk can support public-source governance-economics monitoring: proposal status tracking, fee-rollout mapping, burn-mechanism review, Foundation / Labs budget-context checks and delegate accountability questions. The output is read-only monitoring, reporting and decision-support — not voting guidance, token-market analysis, asset guidance or a governance verdict.

Caveat

This brief is based on public-source monitoring and is intended for educational governance analysis only. It is not investment advice, voting guidance, token-market analysis, legal advice, accounting advice, tax advice or a governance verdict. Protocol fees, burn mechanics, growth budgets, Foundation / Labs operating context and multichain rollout status should be read as source-supported monitoring surfaces, not as proof of future token value, revenue quality, treasury sustainability or completed governance accountability.