Uniswap

UNI governs the protocol that turned automated market making into the default way to trade on-chain. Its most consequential unresolved question is deliberately simple: whether the protocol should charge a fee at all, and if so, who receives it.

The fee switch is the central governance question

Uniswap's core contracts contain a mechanism allowing a portion of trading fees to be diverted from liquidity providers to the protocol. Governance controls whether it is enabled. Turning it on creates protocol revenue and reduces the return to the liquidity providers that make the exchange work — a genuine trade-off with legal and competitive dimensions, which is why it has been debated for years rather than settled.

Immutable contracts constrain governance by design

The core pool contracts cannot be upgraded. Governance can deploy new versions and control peripheral systems, and it cannot alter the behaviour of pools people are already using. This is a deliberate limit on what any future vote can do to existing positions, and it is stronger than any promise.

Hooks turn a pool into a platform

The v4 architecture allows custom code to run at defined points in a pool's lifecycle — before a swap, after a position changes — enabling dynamic fees, on-chain limit orders and custom oracle behaviour without forking the protocol. It shifts Uniswap from a fixed product to a base layer others build on, and it means a pool's behaviour now depends on which hook it uses.

What UNI does and does not capture

UNI votes. It does not automatically receive fees, is not required to trade and is not consumed by usage. Its value case rests entirely on governance rights over a protocol that could, if holders chose, direct revenue to them. That conditional is the whole investment thesis and should be read as such.

Where the protocol sits

Uniswap remains the reference implementation for on-chain trading and the deepest venue on most Ethereum pairs. Its competitive pressure comes from aggregators that route around any single venue and from chains where its deployment is not the default.