How the Uniswap Fee Switch Turns Protocol Fees Into UNI Burns

You buy a governance token after a screenshot of coins leaving supply, then wait thirty days for a deposit that would look like a paycheck arriving at your address. Protocol fees can shrink outstanding coins and still leave that wallet unchanged, because a burn is a supply path rather than a monthly check.

A fee switch is the governance setting that sends a slice of pool swap fees to the protocol instead of leaving the whole fee with liquidity providers, and that slice collects in a per-chain contract. Coins leave total supply when a caller burns the governance token to take those collected assets.

Collectors, releasers, and one-time treasury burns are the machinery of that path: the collector is a contract, the releaser is the exit that pays a caller in those collected assets, and a treasury action is a separate, dated vote. Mixing those three is how a screenshot of destroyed coins gets treated as income.

UNI is Uniswap's governance token, and the fee switch is how a slice of swap fees can become a UNI burn. What Uniswap is names the protocol. The UNI token names what the coin does, including the burn bound, so the slice sits in TokenJar before Firepit can burn anything.

How a swap fee reaches TokenJar

A protocol fee is a slice of a pool swap fee that goes to the protocol. On each chain, adapters send those tokens into one collector called TokenJar. The 80 UNI in a wallet you control stay outside that collector. The jar is a contract, and only the active releaser can withdraw from it.

Every Uniswap swap still pays a fee, and liquidity providers can earn the LP share in a pool they joined, which is a different claim from the protocol slice. The generic picture of how automated market makers (AMMs) work is the pool that prices the swap, so the fee-switch fact is what happens to the protocol portion after that swap.

Uniswap's protocol-fee docs name the collector and the burn exit together. "Each chain has one immutable contract called the TokenJar." All fee sources on that chain send tokens there. Adapters sit in front of the jar and define how a version or product collects. "Assume 100 UNI is the threshold amount for the Firepit Releaser." When the top assets in TokenJar are worth slightly more than that 100 UNI, a caller is paid in those assets for burning the required UNI, and Firepit.release() is user-triggered (source: Uniswap Docs, Protocol fees). Treat that 100 as the docs' worked number, a teaching example.

Suppose you swap USDC for ETH in a pool that has the protocol slice on. The trader fee you pay arrives as the pool's fee assets, so part of it can still accrue to LPs in that pool. Part of it, if the switch is on for that pool, goes to TokenJar on that chain as the tokens the pool actually collected. Those tokens might be USDC, ETH, or whatever the pool took as the fee asset, and they stay jar inventory.

Governance can change which releaser a TokenJar uses, and it can adjust adapter settings, while the jar contract itself is immutable. A passed fee-parameter vote changes rates and switches the contracts already expose. It leaves the jar in place, and it leaves your 80 UNI as wallet inventory.

Keep one picture: swap first, adapter next, TokenJar as the collector, with Firepit as how value leaves that collector. On Ethereum the gas for those calls is still ETH, and how Ethereum works is that chain picture.

Firepit turns jar tokens into a UNI burn

Firepit is the releaser that burns UNI so a caller can take assets out of TokenJar, and anyone can send the release call. Holding UNI in a wallet leaves you as a holder, so the docs' worked threshold stays teaching copy.

That caller is often described as a searcher, so suppose a searcher sees TokenJar holding assets worth slightly more than the 100 UNI example. The profit, when it exists, is the gap between those jar assets and the UNI that gets burned. If the jar is thin, nobody calls, and fees can sit until the gap is worth the burn plus gas. Your 80 UNI stay at the same address when a searcher burns 100 UNI somewhere else. Your share of outstanding coins can change as supply changes, which is market math, and it is still a change in supply.

On Ethereum mainnet, burned UNI is sent to a dead address so those coins leave supply. The protocol-fees README states the same sequence: a searcher pays a fixed UNI amount to the releaser, and then UNI is sent to a dead address so supply falls. For OP Stack L2 chains (Unichain, Optimism, Base, and the like) where only bridged UNI exists, the same README names a two-stage burn that still ends at that mainnet dead address (source: Uniswap protocol-fees README). That path is a bridging detail for those L2s, and it leaves your wallet balance where it was.

The exit rule is the same whether you read the protocol-fee docs or a later vote recap: tokens leave TokenJar when UNI is burned, which is a different event from a treasurer signing a weekly UNI wire to holders.

Which pools send a protocol slice

Protocol fees vary by Uniswap version and by chain. Two July 27, 2026 votes set what is on: Tally 100 recaps v2 and v3 on 11 chains and a v4 subset, and Tally 99 adds v2 and v3 on Robinhood Chain, while the official fees page can lag those votes.

Tally 100's summary says protocol fees are now live across all v2 and v3 pools on 11 chains: Ethereum, Arbitrum, Base, Celo, OP Mainnet, Soneium, X Layer, Worldchain, Zora, BNB Chain, and Polygon. The same text activates v4 protocol fees on a subset, naming Ethereum, Arbitrum, Base, BNB Chain, Polygon, Optimism, and Robinhood Chain, so v4 is a subset of pools on some chains. "The remaining five chains (Celo, Soneium, Worldchain, X Layer, Zora) will be addressed in a subsequent proposal." Those five already sit in the 11-chain v2 and v3 recap. They wait on a later v4 vote (source: Tally, Uniswap proposal 100).

Tally 99 is the same-day Robinhood expansion that list omits, and the proposal text says this onchain vote enables v2 and v3 fees specifically (source: Tally, Uniswap proposal 99). v4 on Robinhood sits in Tally 100's subset, rather than in Tally 99.

The official fees page, fetched September 5, 2026, still describes an earlier rollout. Protocol fees are a portion of swap fees directed to the protocol, and the same page still says protocol fees are active on all v2 pools and select v3 pools, with v4 fee adapter flows enabled through governance (source: Uniswap Docs, Fees). Those last clauses are the lag, because Tally 100 already turned a v4 subset on.

v3 pools also have fee tiers, so a 0.05 percent pool and a 0.30 percent pool are different markets for the same pair, and once the protocol slice is on, it is set by tier.

v2 is simpler: after the switch, the pair still charges 0.30 percent. The docs table splits that as 0.25 percent to LPs and 0.05 percent to the protocol, so the trader fee stayed at 0.30 percent. The fill that keeps the product in line belongs with how Uniswap works, and the fee-switch fact is only that later cut.

Treat those rates as current settings, which governance can change again. A pool with the slice off still pays LPs, and a v4 pool outside the named families in Tally 100 can still trade without that protocol slice.

What UNIfication switched on

UNIfication is the December 2025 vote that turned protocol fees toward a UNI burn. Tally proposal 93 is that vote, titled UNIfication, and Tally's execute date is December 27, 2025 UTC. Those dates belong here as mechanism context, which is a different claim from a price call.

Tally 93 asked governance to turn on Uniswap protocol fees and use those fees to burn UNI. It also sent 100 million UNI from the treasury to the burn address as a one-time action in that proposal (source: Tally, Uniswap proposal 93). That transfer is a historical governance action.

The first rollout was gradual, so v2 pools and a set of v3 pools on Ethereum mainnet came first. Tally 94 executed March 6, 2026 and put the every-pool v3 adapter on mainnet plus Arbitrum, Base, and OP Mainnet, so protocol fees would be active on every v3 pool if that proposal passed. The same text splits a parallel vote for Celo, Soneium, Worldchain, X Layer, and Zora (source: Tally, Uniswap proposal 94). Tally 96 executed June 1, 2026 and extends the infrastructure for collecting and burning protocol fees to BNB Chain and Polygon (source: Tally, Uniswap proposal 96). Tally 99, executed the same calendar day as Tally 100, covers v2 and v3 fees on Robinhood Chain. Count each proposal's executed text, and leave Tally 100's chain inventory in the pools section above. Each of those votes is a fee-parameter change.

Holders have governance rights and are represented through DUNI. "UNI holders have no individual or pro-rata claim on protocol revenue," and value accrual is mediated through the burn, or through any other distribution governance may later authorize (source: Uniswap Docs, UNI token). If a later vote authorizes a different distribution, that would be a new setting, so today's path is still burn-to-release.

The UNI token page, fetched the same day as the fees page, still says protocol fees are currently active only on Uniswap v2 and v3. That line lags Tally 100's v4 subset the same way the fees page lags the all-v3 state. Use the executed Tally text for on and off, and use the docs for TokenJar, Firepit, and the claim bound.

Your 80 UNI stayed a vote coin with a supply path attached. How UNI has traded across cycles is history, which is a different claim from a promise that this path pays you, and UNI across market cycles covers that history. The fee switch is product context there.

LP fees, Unichain sequencer fees, and the same burn

Three different fees can sit near the same ticker: liquidity-provider fees stay with the pool position, protocol fees go to TokenJar then toward a UNI burn, and Unichain sequencer fees, after named costs, join that same burn. Mixing the three is how people wait for a UNI drop after they paid gas on an L2.

LP fees are the share a position earns while it is in range, or while it is the active v2 inventory. Collecting those fees sends the pool tokens to the wallet that holds the position. That collect is a pool payout, so it skips Firepit and it skips a requirement that you burn UNI, while protocol revenue stays in the jar. If you are outside the pool, you have no LP share to collect.

Unichain is an OP Stack L2, a different thing from the AMM and from the UNI token. Sequencer fees are what users pay to get transactions included on that chain, and the UNIfication post is dated November 10, 2025. "This proposal directs all Unichain sequencer fees, after L1 data costs and the 15% to Optimism, into the burn mechanism" (source: Uniswap Blog, UNIfication). Read the commas: L1 data costs come off first, Optimism's 15 percent comes off, and what remains is what the proposal sends to burn. The remainder named here is another inlet into the same TokenJar and Firepit path.

Tally 100 is a pool-fee vote for a v4 subset, so it leaves Unichain sequencer burns on the path UNIfication already set. UNIfication, Tally 93, is the proposal that already directed the sequencer remainder into the burn. A banner that says the fee switch is on is talking about AMM protocol fees unless it names Unichain.

UniswapX can also be a fee source in the protocol-fee architecture, and it is still a signed-intent auction. UniswapX as an intent auction is that fill path. An UniswapX fill swaps the tokens in the order, while the protocol-fee path, where it is on, is a separate collector, so the fill itself is separate evidence from a UNI burn in your wallet.

You can use Unichain, swap on a v2 pair, and hold UNI, all at once. Paying sequencer gas leaves your UNI balance unchanged, and collecting LP fees leaves TokenJar unchanged. Only the searcher path, or a later authorized distribution, moves value out of the jar.

What to weigh before you treat a burn as income

Treat the fee switch as a supply path first, then check which fee you actually paid or earned. A holder paycheck, an LP collect, and a Unichain gas payment are different purposes. Your 80 UNI only count for the screen that actually holds them, and Firepit is the caller who burns UNI.

Four checks are enough to name the fee you actually paid or earned.

• If the purpose is a holder deposit, ask whether any contract was told to send UNI to your address, because TokenJar pays the Firepit caller in jar assets.
• If the purpose is an LP fee, ask whether you have a position in that pool, because the protocol slice is a different claim from the LP share.
• If the purpose is Unichain, ask whether you paid sequencer gas, because that remainder joins the burn after named costs and still leaves the gas-paying wallet unchanged.
• If the purpose is a CEX fill, read whether the screen says UNI/USDT spot, UNIUSDT, or UNIUSD, because those products share a ticker and Firepit is an onchain call.

BloFin has listed UNI/USDT on spot since January 15, 2024. BloFin lists two UNI perpetuals: UNIUSDT at up to 75x, listed January 12, 2023, and UNIUSD, an inverse contract settled in UNI, at up to 20x, listed June 27, 2025.

Uniswap is a competing DEX, and BloFin is a centralized exchange that lists UNI, so both sentences can be true at once. The generic fork is centralized versus decentralized exchanges. A listing date tells you when this CEX market went live, which is a different fact from TokenJar access.

Price reaction to a burn is a driver question, and what moves the UNI price covers those drivers. A live burn total is a dashboard figure, and it stays out. The docs' 100 UNI example is a teaching number. Size any holding after you know which fee path you actually wanted, and how to invest in crypto is the generic holding picture.

A screenshot of a burn is proof that UNI left supply, and it is still a supply event.

Common questions about the Uniswap fee switch

Does every Uniswap v2 pair pay a protocol fee into TokenJar?

The chip names the AMM version of that pair. Tally 100 recaps v2 as a vote family on named chains, and it leaves per-pair collection as a later check against the executed text. An old v2 pair can sit in that family and still leave a thin jar, or sit on a chain the vote left out, so match chain plus version to the executed text, then stop. The chip is a version label.

If I hold UNI on BloFin, can I call Firepit.release from the exchange?

Firepit.release is an onchain call, and a BloFin UNI/USDT balance is a venue credit until you withdraw it to a signing wallet. UNIUSDT is a perpetual, so closing it leaves UNI off that wallet. Even after a spot withdrawal you still have to burn the required UNI and pay gas on the chain where that TokenJar lives, and support leaves the release to the signing wallet. If the screen is an exchange balance, you are still a venue holder rather than the Firepit caller.

If TokenJar is on BNB Chain, does Firepit use the same two-stage bridged burn as Unichain?

The protocol-fees README's two-stage sentence is scoped to OP Stack L2 chains (Unichain, Optimism, Base, and the like) where only bridged UNI exists. BNB Chain and Polygon sit in Tally 100's v2 and v3 recap, and they sit outside that OP Stack sentence. Copying Unichain's bridge steps onto BNB is a different path from what the README describes. Read the releaser path published for that chain, because each non-mainnet burn has its own published walk.

If I swapped on Arbitrum, which chain's TokenJar holds the protocol slice?

The Arbitrum TokenJar holds that slice, because each chain has one collector. An Arbitrum pool sends its protocol tokens to the Arbitrum jar. Firepit.release for that slice has to run on Arbitrum, with gas and UNI on Arbitrum. Watching a mainnet burn address leaves the Arbitrum jar as its own question, so if you swapped on Ethereum, look at Ethereum's jar instead.

If UNI sits in a v3 position, does Firepit burn that UNI?

UNI deposited as liquidity is inside the pool. Firepit burns UNI that the caller supplies to release TokenJar assets. Your position can still earn the LP share while it is in range. Collecting that share credits the pool assets to the NFT owner, and those coins stay as pool assets until you withdraw. If you want that UNI out of the pool, you withdraw the position. That withdraw is a liquidity exit.

If a searcher already released TokenJar, can I call Firepit.release on the same assets?

Release pays the caller in the tokens that left the jar, so those coins have already left for that caller. A later release only works if new protocol fees have accrued past the threshold again. Replaying someone else's successful hash leaves the same USDC with the original caller. If the jar is thin after that call, waiting is the documented behavior.

If I close UNIUSD, does the UNI settlement let me call Firepit from BloFin?

UNIUSD is an inverse perpetual, UNI-settled, so profit and loss is in UNI as a venue credit. That credit still sits on BloFin until you withdraw UNI to a signing wallet. Closing the contract is a derivative settlement. After withdrawal you still have to be the onchain caller, with gas, on the chain that holds the jar. UNIUSD can credit UNI while UNIUSDT settles in USDT, and neither fill is TokenJar access.

Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated September 2026. Primary sources include the Uniswap protocol-fee docs, the Uniswap fees page, the UNI token docs, the UNIfication blog, and Tally proposal 100. All facts independently verified against cited documentation current as of September 2026.

This article is educational and general in nature, not financial or investment advice. Cryptocurrencies like UNI carry real risks, including price volatility, venue custody risk, smart-contract risk in fee adapters and releasers, and the chance of losing funds. Nothing here is a recommendation to buy, sell, hold, or participate in any project. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.