0x6ff3710f6ff3…6ff3710c

ConfirmedDeFi434 vB179 sat/vB2 min decode

Uniswap Seeks New X Layer Route for Fees Stuck in TokenJar

A bridge incompatibility left roughly $300,000 in X Layer fees stranded in Uniswap's TokenJar. A Snapshot vote on a replacement release route runs Nov. 15-20.

Uniswap Seeks X Layer Fix for Fees Awaiting a Corresponding UNI Burn
WitnessUniswap Seeks X Layer Fix for Fees Awaiting a Corresponding UNI BurnAI-generated

Outputs

  1. Roughly $300,000 in X Layer protocol fees are stuck in Uniswap's TokenJar, an unconfirmed estimate.

  2. X Layer's OP Stack bridge rejects ERC-20 tokens including UNI; Agglayer handles token transfers on the chain.

  3. Proposed releaser starts at an 80,000 UNI payment threshold declining toward the 2,000 UNI floor.

  4. Snapshot vote on the replacement runs Nov. 15-20; the proposal payload remains marked Draft.

Uniswap Labs is asking governance to approve a replacement fee-release route on X Layer after a bridge incompatibility stranded an estimated $300,000 in protocol fees, according to the proposal filed on Snapshot with voting open Nov. 15-20.

The problem stems from X Layer's infrastructure rather than from Uniswap's broader burn program. The releaser installed when protocol fees were activated on X Layer followed an OP Stack pattern used on other chains. X Layer's OP Stack bridge, however, rejects ERC-20 tokens, including UNI. Token transfers on X Layer run through Agglayer instead.

The consequence is operational, not cosmetic. Fees accumulated in the TokenJar, but the existing route could neither release them nor complete the corresponding UNI burn. Uniswap states the failure does not indicate that burns stopped across the protocol.

What does the proposed fix change?

The replacement would route releases through X Layer's token-transfer bridge and raise the initial payment threshold. Under the proposed settings, a payment starts at 80,000 UNI and declines toward the standard 2,000 UNI floor.

The mechanics work as follows:

  • A permissionless searcher pays UNI to claim fee assets from the TokenJar.
  • That UNI payment is burned when the release completes.
  • The higher starting threshold is designed to direct more of the backlog's value toward burns.

The specific settings remain proposals, not deployed parameters. Uniswap estimates roughly $300,000 in fees available for a sweep, while noting that figure is not a confirmed current TokenJar balance.

Will UNI actually be burned?

Not automatically. The amount of UNI ultimately burned depends on a successful release and on the terms searchers accept. Fee accrual by itself does not trigger an open-market purchase of UNI or complete a burn. In other words, the stranded balance converts into burned supply only if a searcher finds the economics worthwhile at the proposed thresholds.

The TokenJar is the container for collected protocol fees across Uniswap deployments; its release mechanism lets a searcher exchange UNI for designated fee assets. Uniswap Labs has separately opened TokenJar fee conversion to outside applications, letting apps collect fees in one selected asset even when users pay in different tokens. The X Layer issue concerns only the route for Uniswap protocol fees.

What happens next?

The Snapshot vote on the replacement runs through Nov. 20. The broader proposal payload remains marked Draft, and no deployment or successful release has been confirmed. Governance participants will effectively decide whether to authorize the higher 80,000 UNI starting threshold and the Agglayer-compatible bridge route before any UNI reaches the burn address.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles