Dashboard · VantagePlanned

Uniswap Fee Switch: UNI Burned and Protocol Fees

How much UNI has been burned since the Uniswap fee switch went live?

UNI burned since the Uniswap fee switch went live, the protocol fees that pay for each burn and the UNI supply left after them.

ShareEmail itvoltfincrypto.com/apps/uniswap-fee-switch-uni-burn
Blueprint

What the dashboard will show.

The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

  • Period
  • Fee source

Burns

UNI burned, releases and supply net of burns.

UNI burned by fees, to date

UNI

UNI burned through releases since the fee switch went live, excluding the one-time treasury burn.

Figureprotocol_revenue_dailyAwaiting data

UNI burned, 30 days

UNI

UNI burned through releases over the last thirty days.

Figureprotocol_revenue_dailyAwaiting data

Releases, 30 days

count

Release transactions in the last thirty days, each one burning UNI to claim the fees collected.

Figureprotocol_revenue_dailyAwaiting data

UNI supply net of burns

UNI

UNI totalSupply() at the latest daily block minus the balance of the burn address.

Figuretoken_supply_dailyAwaiting data

UNI burned by day

UNI

UNI burned each day from the releases in that day, with the treasury burn marked apart.

Bar chartprotocol_revenue_dailyAwaiting data

Every release

Each release with its block, time, UNI burned, the tokens claimed, their value at the same block and the releasing address.

Tableprotocol_revenue_dailyAwaiting data

Fees

Protocol fees collected, waiting and by source.

Fees collected, 30 days

USD

Protocol fees that reached the TokenJar in the last thirty days, at oracle prices.

Figureprotocol_revenue_dailyAwaiting data

Fees waiting

USD

Fees held in the TokenJar at the latest block, which the next release would claim.

Figureprotocol_revenue_dailyAwaiting data

Fees by source

USD

Fees collected over the period by source: v2 pools, v3 pools and Unichain sequencer revenue.

Donutprotocol_revenue_dailyAwaiting data

Fees collected and UNI burned

USD

Fees collected and the value of UNI burned each week, showing how closely burns follow fees.

Line chartprotocol_revenue_dailyAwaiting data

Period
Last 30 or 90 days, or since the fee switch went live
Fee source
v2 pools, v3 pools, Unichain sequencer or all
About

What it answers, and for whom.

Uniswap's fee switch turns a share of pool trading fees into protocol fees. Under the UNIfication proposal, which governance passed in December 2025, those fees and Unichain sequencer revenue collect in a contract called the TokenJar, which releases them only to someone who burns UNI in a second contract, the Firepit. This dashboard follows that loop: fees in, UNI burned and the supply left.

A release happens when the fees waiting are worth more than the UNI it costs, so burns arrive in steps rather than with every trade. The dashboard lists every release with its transaction and adds burns up by day and month. It keeps the one-time burn from the treasury that came with the proposal apart from the ongoing burns paid for by fees.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. UNI burned is read from UNI Transfer logs into the burn address used by the Firepit, each matched to the release transaction it paid for.
  2. Fees in are the TokenJar's inflows: Uniswap v3 CollectProtocol transfers, v2 fee-to LP tokens and Unichain sequencer fee transfers, each valued at that day's oracle price.
  3. A release is a transaction that burns UNI and moves tokens out of the TokenJar; its value is the tokens released at oracle prices, set beside the value of the UNI burned at the same block.
  4. UNI supply net of burns is totalSupply() at the daily block minus the balance of the burn address, since burned UNI is sent there rather than removed by the token contract.
  5. The one-time treasury burn approved with UNIfication is shown on its own line and kept out of fee-funded totals.

The data it needs

Read from chain state and history

  • protocol_revenue_dailyTo buildProtocol fees, revenue and buybacksFees users paid to each protocol and the part kept by the protocol or its token holders, per protocol and day, including buybacks.
  • token_supply_dailyTo buildToken supply by dayTotal supply of each registry token on each chain at day end: wrapped BTC, liquid staking tokens, tokenized assets and other tracked tokens.
  • dex_swaps_dailyTo buildDEX volumeSwap counts and volume per DEX, pool and chain per day, decoded from Swap events, valued with stablecoin legs and oracle prices.
  • native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
  • UNI Transfer logs to the burn address
  • Fee-collector and UNI-burn contracts introduced by UNIfication: fee deposits into the TokenJar and UNI burned per Firepit release
  • Uniswap v3 CollectProtocol events and v2 feeTo LP mints
  • Unichain sequencer fee transfers to the burn mechanism
  • UNI totalSupply() at daily blocks
Questions

Questions people ask.

What is the Uniswap fee switch?

A setting in Uniswap's contracts that sends part of each pool's trading fees to the protocol instead of all of it to liquidity providers. It existed in the code for years and was turned on through the UNIfication proposal that governance passed in December 2025.

How does UNI get burned?

Protocol fees collect in the TokenJar, and anyone can claim them by burning a set amount of UNI in the Firepit. Claiming is worthwhile when the fees waiting are worth more than that UNI, so whoever claims the fees pays for the burn.

Which pools pay protocol fees?

UNIfication turned fees on for Uniswap v2 and a set of v3 pools on Ethereum first, and routes Unichain sequencer revenue the same way. More pools, versions and chains need their own governance votes, and the dashboard adds each source as it goes live.

Does burning UNI lower its total supply?

Burned UNI is sent to an address no one controls, so it can never move again, but the token contract's totalSupply still counts it. The dashboard shows both: total supply as the contract reports it and supply net of burned UNI.

Are Uniswap's protocol fees paid to UNI holders?

No. The fees are not distributed; they are claimed by whoever burns UNI, so their effect on holders comes through the burn. The dashboard reports fees and burns as measured and leaves their valuation to the reader.

Fee switch
The parameter that diverts a share of each pool's swap fees from liquidity providers to the protocol.
UNIfication
The Uniswap governance proposal, passed in December 2025, that turned on protocol fees, routed them to UNI burns and burned UNI from the treasury.
TokenJar
The contract where Uniswap protocol fees accumulate until someone releases them by burning UNI.
Firepit
The contract where UNI is burned, by sending it to a dead address, to release the tokens held in the TokenJar.

Build Uniswap Fee Switch: UNI Burned and Protocol Fees on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.