Uniswap has a system designed to turn trading fees into permanently burned UNI tokens.
On X Layer, the first half is working. The second isn’t.
Protocol fees have been accumulating on the network, but the mechanism responsible for releasing those funds and burning UNI cannot complete its job.
And this isn’t a problem Uniswap discovered yesterday.
The issue was identified in late September. Yet, more than six weeks later, the proposed repair was still moving through governance and development.
The explanation involves a bridge that can deliver governance instructions but cannot carry the token those instructions are supposed to burn.
The Bridge That Broke the Burn
Uniswap’s fee mechanism is supposed to work without the protocol directly swapping its revenue into UNI.
Trading fees accumulate in a contract called TokenJar. Anyone can then pay a predetermined amount of UNI to claim the collected assets. The UNI used for that payment is permanently burned.
On X Layer, the normal release threshold is 2,000 UNI.
But according to Uniswap Labs’ November 6 governance proposal, X Layer’s existing releaser was designed for the wrong token-transfer route.
The network runs on the OP Stack, but it uses Agglayer for token transfers.
Meanwhile, the OP Stack bridge that delivers governance messages rejects ERC-20 transfers, including UNI.
Uniswap deployed a releaser following the standard OP Stack design without making it compatible with X Layer’s separate token bridge.
The result is an unusual split: fees continue accumulating, but the releaser cannot process them through the intended UNI-burning mechanism.
Importantly, this does not mean every Uniswap burn has stopped. The problem concerns the fee-release infrastructure on X Layer.
A March Launch, a September Discovery, and an Unfinished Fix
The timeline makes the situation more revealing.
Uniswap governance executed Proposal 95 on March 8, approving protocol fees on X Layer alongside several other networks.
By late September, the bridge incompatibility had been identified.
On October 23, developers opened a pull request for a replacement X Layer releaser.
Then came the November 6 governance proposal outlining the repair.
Ravel calculated that 252 days elapsed between Proposal 95’s execution and November 15. That figure measures the age of the governance rollout, not the precise duration of fee accumulation or the amount of UNI that should have been burned.
The existing infrastructure provides another useful reference.
Uniswap’s official deployment registry still lists X Layer’s TokenJar at 0x8Dd8B6D56e4a4A158EDbBfE7f2f703B8FFC1a754, alongside its original OptimismBridgedResourceFirepit releaser.
Meanwhile, Proposal 103’s implementation pull request remained marked as a draft when Ravel checked on November 15.
The proposed replacement is therefore documented, but the available development records do not establish that the repair has been executed on-chain.
The Fix Has Another Problem to Solve
Replacing the bridge route isn’t the entire solution.
Because fees have accumulated without being released, immediately returning to the normal 2,000 UNI threshold could create an opportunity for searchers to claim an unusually valuable backlog at a fixed cost.
Uniswap wants to prevent that.
Its proposed DecayingThresholdSetter would initially require a higher UNI payment, then gradually lower the threshold to 2,000 UNI over roughly six days after execution.
That introduces a second economic question: how much value has actually accumulated?
Uniswap Labs confirms the accumulation, but the reviewed disclosures do not quantify the outstanding assets. Ravel could not independently reconstruct the TokenJar’s complete asset balances or transaction history through November 15.
Without those figures, calculating the unrealized UNI burns would be speculative.
The distinction matters. As Ravel previously explored in Lido’s automated buyback system, a mechanism designed to support token value does not necessarily produce purchases or burns simply because the underlying protocol generates revenue.
And unlike Pyth’s treasury-held token purchases, Uniswap’s model is designed to permanently remove the UNI paid during successful fee releases.
That makes execution particularly important.
There is no verified evidence that the X Layer problem caused UNI’s recent price decline. Nor does this case demonstrate that Uniswap’s broader fee-burning infrastructure has failed.
What it does reveal is a gap between the economics promised by a cross-chain fee mechanism and the infrastructure required to deliver them.
Uniswap built a system where trading activity could eventually remove UNI from circulation.
On the X Layer, the trading fees arrived.
The burn is still waiting for the bridge.
Ravel Methodology
Ravel reviewed Uniswap governance proposals 95 and 103, the November 6 RFC and subsequent developer responses, official deployment records, and the October–November implementation pull requests.
The 252-day interval is calculated from March 8 through November 15, 2026. It does not measure continuous fee accrual. The current outstanding TokenJar balances and total unrealized UNI burns were not independently established through transaction-level verification.
The article distinguishes documented protocol behavior from completed on-chain execution and does not attribute UNI’s market performance to the X Layer issue.


