0x38d56a9f38d5…38d56a9c

Confirmed683 vB177 sat/vB3 min decode

Uniswap Moves to Unlock $300,000 in Stranded Fees on X Layer

Uniswap froze about $300,000 in X Layer fees after its relayer rejected ERC-20 transfers, halting $UNI burns and prompting a draft auction redesign.

Uniswap freezes $300,000 in stranded fees, halting automatic token burns
WitnessUniswap freezes $300,000 in stranded fees, halting automatic token burnsanncapictures / pixabay

Outputs

  1. Roughly $300,000 in protocol fees are stranded on X Layer after its relayer rejected ERC-20 transfers, halting $UNI burns.

  2. Proposal 95 executed March 8; PR 167 proposes an 80,000 $UNI starting threshold with a 2,000 $UNI floor and two-day half-life.

  3. Strata Terminal reported $7.8 million in $UNI burns over 30 days as of Nov. 15 and 14.1 million UNI in recurring burns overall.

  4. As of Nov. 15, PR 169 remained a draft, with setter and replacement releaser deployment listed as blockers.

Uniswap has frozen roughly $300,000 in accrued protocol fees on X Layer after the network's relayer rejected the ERC-20 transfers needed to complete scheduled $UNI burns, forcing governance to redesign how the backlog is released.

The breakdown traces back to Proposal 95, which recorded execution on March 8, including X Layer fee-activation actions. According to Uniswap Labs, the installed relayer followed the standard OP Stack token-bridging pattern, but X Layer's implementation diverges: governance messages use the OP Stack bridge, while token transfers use Agglayer, and X Layer's version rejects ERC-20 transfers — including $UNI.

Converting accrued fees into a completed burn requires a searcher to execute the exchange and the bridge to settle it. Under the current design, the searcher pays in $UNI toward the burn and keeps the recoverable asset value above that payment and its execution costs. Because the searcher's surplus is a separate return, a release does not require Uniswap itself to buy $UNI on the open market at the moment of release.

What does the freeze change for practitioners?

The immediate consequence is a stalled burn pipeline on one chain and a fixed-price arbitrage waiting to be claimed. Uniswap's collection architecture requires explicit collection calls for v3 and v4 fees, meaning a jar's wallet balance alone does not capture everything accrued in pools — the true backlog may exceed visible balances. The edited description of implementation PR 167, opened Nov. 2, estimates roughly $300,000 of fees could be swept into the jar and warns that restarting with the existing 2,000 $UNI payment could hand the accumulated assets to the first searcher at that fixed price.

The proposed replacement releaser would use X Layer's actual token-transfer route to complete the burn, routing around the Agglayer incompatibility that stranded the fees in the first place.

An auction instead of a fixed payment

PR 167 replaces the flat 2,000 $UNI claim cost with a decaying auction. The parameters:

  • An initial threshold of 80,000 $UNI
  • A floor of 2,000 $UNI
  • A two-day half-life, with roughly 10.8 days estimated to reach the floor

The mechanism starts with an expensive claim and reduces the required payment over time. A searcher acts when the assets it can recover justify the payment and its costs. Competition, in theory, directs more of the backlog value into $UNI burn payments rather than leaving the margin created by a low fixed threshold to the first mover.

The published plans remain internally inconsistent: a Nov. 6 forum post describes the decay reaching the floor in roughly six days after execution, while the reviewed implementation describes about 10.8 days. Governance would start the decay only after the TokenJar points to the new releaser. Anyone could update the threshold, and searchers could bundle that update with a release transaction.

Ownership mechanics carry a constraint worth noting. The setter would temporarily own the releaser, returning ownership and threshold-setting control to governance on the first update at the floor. The reviewed design removes a separate reclaim function, so elapsed time alone would not restore control — governance depends on a searcher eventually executing at the floor.

Scale and open items

As of Nov. 15, PR 169's combined implementation remained a draft, listing the setter and replacement releaser deployment as blockers. The releaser and setter PRs remained open, and the official deployment registry still listed X Layer's original releaser.

For scale, Strata Terminal reported $7.8 million in $UNI burns over the 30 days preceding Nov. 15, and 14.1 million $UNI in recurring burns overall — separate from the one-time 100 million $UNI treasury burn. That recurring flow contextualizes the proposed one-time release, though the older $300,000 backlog estimate uses a different observation date and valuation method, so a direct conversion ratio would conflate an estimated stock of fees with realized burn flows.

The decisive test of the repair is how much $UNI the release payment ultimately delivers to Ethereum's burn address once the setter and replacement releaser ship.

via cryptonews.net (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,512 articles