Uniswap’s UNIfication ballot put the fee switch before UNI voters

Uniswap governance had its final UNIfication ballot open on December 20, 2025, putting one of decentralized finance’s longest-running economic questions to an onchain vote: whether a portion of trading activity should begin generating protocol fees linked to destruction of the UNI governance token.

The proposal had not passed on December 20. Approval would trigger eight onchain calls, including transferring 100 million UNI from the governance treasury to an unusable burn address, changing the Uniswap v2 fee recipient and placing the v3 factory under a new fee controller. It would also approve 40 million UNI for a two-year growth program and record contractual agreements between DUNI—the association representing Uniswap governance—and Uniswap Labs.

That combination made the ballot more than a token-supply vote. It joined protocol economics, software stewardship and organizational governance in one executable package.

How the proposed fee system worked

Under the proposal, Uniswap v2 liquidity providers would receive 0.25% of each swap instead of the full 0.30%, while 0.05% would become a protocol fee. For selected v3 pools on Ethereum mainnet, the protocol would initially receive one-quarter of liquidity-provider fees in the 0.01% and 0.05% tiers and one-sixth in the 0.30% and 1% tiers.

The proposal’s authors said the initial v3 pool list represented 80% to 95% of liquidity-provider fees on Ethereum mainnet. That range was a proponent-supplied estimate, not a Coinburn calculation, and the governance materials did not provide a single event-day measurement window suitable for independent reproduction.

Collected assets would enter an immutable TokenJar contract. A separate Firepit mechanism would require UNI to be burned before accumulated fee assets could be released. Consequently, the design did not promise dividends, distributions or a direct claim on revenue to individual UNI holders. Its economic link was supply reduction: protocol use could cause UNI destruction if the proposed contracts operated as intended.

The one-time transfer of 100 million UNI was described by the authors as a retroactive estimate of tokens that might have been burned had protocol fees operated from UNI’s September 2020 launch. It was a policy choice encoded in the proposal, not an audited reconstruction of foregone fees.

Governance and institutional stakes

UNIfication also proposed moving most functions historically performed by the Uniswap Foundation—including ecosystem support, governance support and developer relations—to Uniswap Labs. Labs, in turn, would set its interface, wallet and API fees to zero and operate under a services agreement with DUNI.

A growth budget of 20 million UNI per year was scheduled to begin on January 1, 2026, distributed quarterly through a vesting contract. The executable proposal authorized 40 million UNI, covering two years, while leaving unvested tokens in the treasury and subject to cancellation.

The structure created a clear tradeoff. Proponents argued that protocol fees, token burns and consolidated development would align the ecosystem. Governance participants had also raised concerns before the final ballot about reduced liquidity-provider fees, the scale of the growth budget, concentration of operational responsibilities and whether burning all protocol fees was preferable to building a productive treasury.

What was knowable on December 20

The authoritative records established the proposal’s executable actions and showed that voting was active. They did not establish that the measure would pass, that fee revenue would reach any forecast, or that UNI’s market price would respond in a particular direction. This reconstruction therefore makes no event-day price-performance claim and reports no interim vote total, because surviving contemporaneous reports do not provide a consistently reproducible cutoff time.

Later record

The governance portal subsequently recorded execution on December 28, 2025, after 125,342,017 UNI voted for the proposal and 742 voted against it. Those figures are later context and were not available when the December 20 ballot was still open.