Upgrade VolatilePair hook and update X Layer Releaser
Snapshot vote on two Uniswap Labs technical updates: capping the VolatilePair hook temporary fee by block gap on Ethereum, and replacing the protocol fee releaser on X Layer so accrued fees can be released and UNI burned.
Part 1 upgrades the VolatilePair Hook proxy on Ethereum, owned by Uniswap Governance, to a new implementation that caps the temporary fee, applied to trades pushing the price back after a large move, at a maximum number of blocks via a new per-chain parameter, maxTempFeeBlockGap. On Ethereum the value would be 1; Robinhood Chain already runs it with a gap of 2. Changing hook parameters later would need another governance proposal. Part 2 replaces the X Layer fee releaser. Protocol fees activated by Proposal 95 have accrued on X Layer but cannot be released because the existing OP Stack releaser cannot bridge UNI over X Layer's Agglayer bridge, so the corresponding UNI has not been burned. Uniswap Labs wrote an AggLayerReleaser and a DecayingThresholdSetter that starts with a high release threshold and steps down to the standard 2,000 UNI over roughly six days after execution, intended to avoid an arbitrage opportunity on the accumulated fees. Governance would point the X Layer TokenJar to the new releaser. Contracts are deployed by Uniswap Labs ahead of the vote. Open points: effects on LP returns and the post-decay threshold.
Free: this site, which you have to remember to check. Paid: every Monday an email lists the votes closing in the next 7 days, sorted by deadline, then the week's items in full.
Sample of the weekly email
Closing in the next 7 days 1. [dao] Proposal title - vote ends 2026-11-16 - one-line summary 2. [dao] Proposal title - vote ends 2026-11-18 - one-line summary The week in full [dao] Proposal title: full plain-English analysis and flags
10 USDC on Base = 31 days.
- Send 10 USDC on Base to
0xdbe64890cbC58304815A865F63151c205F2C88B2 - Email the transaction hash to saleforce@agentmail.to, which is this project's own inbox. Send it from the address that should receive the digest.
- Access starts when the payment is confirmed on-chain.