{"id":31102,"date":"2026-07-29T13:01:19","date_gmt":"2026-07-29T12:01:19","guid":{"rendered":"https:\/\/investx.fr\/en\/2026\/07\/29\/uniswap-v4-hayden-adams-protocol-fees-lp-rewards\/"},"modified":"2026-07-29T13:01:27","modified_gmt":"2026-07-29T12:01:27","slug":"uniswap-v4-hayden-adams-protocol-fees-lp-rewards","status":"publish","type":"post","link":"https:\/\/investx.fr\/en\/crypto-news\/uniswap-v4-hayden-adams-protocol-fees-lp-rewards\/","title":{"rendered":"Uniswap v4: Hayden Adams Hits Back Over Protocol Fees and LP Rewards"},"content":{"rendered":"\n

Uniswap<\/strong> has just activated protocol fees on its v4 pools \u2014 and the backlash was swift. Hayden Adams<\/strong>, founder of the DEX, came out swinging to dismantle what he calls “FUD” surrounding the impact on liquidity providers. But beneath the aggressive PR, a very real technical dispute is dividing the DeFi<\/strong> community.<\/p>\n\n\n\n

Adams pushes back: v4 fees are “additive,” not subtractive<\/h2>\n\n\n\n

On July 28, 2026<\/strong>, Hayden Adams<\/strong> published a series of posts on X refuting two claims that had been circulating in the community: that protocol fees would reduce LP earnings, and that the protocol would capture 25% of LP profits<\/strong>. According to Adams, both readings are simply wrong.<\/p>\n\n\n\n

His core argument: protocol fees are additive<\/strong> to the existing fee structure, not subtractive. Using the example of a 30 basis point (bp)<\/strong> pool, he argues that a 5 bp<\/strong> protocol fee represents roughly 14%<\/strong> of total swap fees \u2014 not a cut taken from the LPs’ share. In his view, an LP who was earning 30 bp per swap continues to earn 30 bp.<\/p>\n\n\n\n

This framing is designed to reassure liquidity providers<\/strong>, whose confidence is critical to maintaining Uniswap’s<\/a> TVL at $3.06 billion<\/strong> according to DefiLlama \u2014 making it the largest DEX<\/strong> by total value locked.<\/p>\n\n\n\n

The v4 documentation tells a different story \u2014 and the math doesn’t hold<\/h2>\n\n\n\n
\"Uniswap<\/figure>\n\n\n\n

The problem is that the official Uniswap v4 documentation<\/strong> describes a sequential<\/em> application of fees: the protocol fee is taken first, and the LP fee is then applied to the remaining amount. This mechanic mathematically implies that the base on which LP earnings are calculated shrinks the moment any positive protocol fee exists \u2014 even if swap volume remains constant.<\/p>\n\n\n\n

The contradiction between Adams<\/strong>‘s public statements and the technical documentation is at the heart of the debate. And the figures he cites deserve scrutiny: 5 bp out of 30 bp is 16.7% of total fees<\/strong> by straightforward division \u2014 not 14% as he claims. The calculation method used to arrive at that figure was not explained in his posts, and no independent source has validated it at this stage.<\/p>\n\n\n\n

This arithmetic ambiguity is fueling distrust among parts of the DeFi<\/a> governance<\/strong> community, who see it as deliberately optimistic communication rather than a rigorous analysis of the real-world impact on active LPs.<\/p>\n\n\n\n

A structural issue for concentrated LPs and UNI token holders<\/h2>\n\n\n\n

Beneath the technical dispute lies a deeper tension: UNI token holders<\/strong> directly benefit from protocol-level revenue capture, while concentrated liquidity LPs<\/strong> \u2014 who bear impermanent loss risk and actively manage their positions \u2014 face a potential squeeze on their effective yield.<\/p>\n\n\n\n

The activation of protocol fees was approved by Uniswap governance<\/strong> across multiple blockchains and on a selection of v4 pools. At the scale of a protocol managing $3.06 billion in TVL<\/strong>, even a marginal shift in fee structure can translate to millions of dollars being redistributed differently between LPs and the protocol treasury.<\/p>\n\n\n\n

The real question, then, is not whether protocol fees exist \u2014 they do \u2014 but whether their structural effect on LP returns is material or negligible in practice<\/strong>. A debate that neither Adams’s posts nor the available documentation currently resolves with any clarity<\/a>.<\/p>\n\n\n\n

\n\n\n\n

Related articles :<\/h3>\n\n\n\n