TLDR
The first major UNI (Uniswap) burn already happened on 28 Dec (UTC), with 100 million UNI destroyed after governance approval Uniswap 100 million burn.
- Ongoing burns are now programmatic via the fee switch and occur as protocol fees accrue, not on fixed dates protocol fee switch and burn mechanism.
- The burn followed a two?day timelock after a vote with 99.9% support; fees for v2 and select v3 pools are live vote and timelock confirmation.
- Future burn pace depends on Uniswap trading volumes and the share of fees directed to the burn mechanism details.
Deep Dive
1. First Burn Date
Uniswap executed the first large-scale UNI burn on 28 Dec, removing 100 million UNI from the treasury after the community approved the UNIfication proposal Uniswap 100 million burn.
This was the governance?mandated retroactive burn and marked a shift in UNI token economics toward deflationary pressure when protocol activity is high vote and timelock confirmation.
The initial burn is done. The supply cut is real and dated. Any future reduction depends on protocol usage rather than preset burn dates.
2. How Future Burns Work
Burns are now tied to Uniswaps protocol fee switch. A portion of trading fees on v2 and selected v3 pools accrues to a programmatic mechanism that periodically destroys UNI, alongside net Unichain sequencer revenue after costs protocol fee switch and burn mechanism.
Community coverage details pool?level fee rates and the routing of fees into contracts (often discussed as TokenJar and Firepit) before UNI is burned protocol fee switch and burn mechanism.
There is no calendar of burn dates. Burns happen as fees accumulate. Higher volumes and fee allocations can mean more frequent or larger burns.
3. Governance Vote And Timelock
The UNIfication proposal passed with 99.9% support and then executed after a two?day timelock. Fees are active on v2 and a curated set of v3 pools on mainnet, and interface fees were set to zero vote and timelock confirmation.
This governance design links protocol activity directly to UNI supply reduction, aligning token value capture with usage rather than static schedules Uniswap 100 million burn.
Watch governance decisions on fee parameters and pool coverage. Changes there can speed up or slow down the burn cadence.
Conclusion
UNIs first major burn occurred on 28 Dec, and future burns are ongoing and usage?driven. There is no fixed burn date; cadence and magnitude hinge on Uniswap volumes and fee settings approved by governance. Monitoring protocol fees and pool coverage is the practical way to gauge burn pace.
CoinsKid.Com