Uniswap

• Name: Uniswap
• URL: https://uniswap.org
• Category: decentralized exchange / AMM protocol
• Tags: ethereum-ecosystem
• Summary: Uniswap is the AMM baseline. The core job is onchain pool pricing and liquidity accounting; most later trading systems are best read as moving decision power above that pool layer rather than replacing it. Keep this note on the protocol itself, and use uniswap-labs when the sharper question is who controls the default web app, wallet, front-end release workflow, and other company-run routing layers most users inherit first.
• What it does:
  • Enables permissionless token swaps directly against onchain liquidity pools
  • Allows liquidity providers to supply token pairs and earn fees
  • Supports market creation without centralized exchange listing processes
  • Evolves AMM design across versions, including concentrated liquidity and newer architectural features in later versions
• Key claims:
  • Uniswap docs describe the protocol as a decentralized exchange built on Ethereum
  • Official materials say the protocol is open-source, non-upgradeable, and designed for decentralization, censorship resistance, and self-custody
  • Docs explain the protocol’s liquidity-pool model and constant-product AMM design, with more advanced concentration/accounting mechanisms in later versions
• Whitepaper: Official Uniswap protocol whitepapers were confirmed during this pass and saved locally:
  • ../whitepapers/uniswap-whitepaper-v2.pdf
  • ../whitepapers/uniswap-whitepaper-v3.pdf
  • ../whitepapers/uniswap-whitepaper-v4.pdf See also ../whitepapers/uniswap-primary-sources-2026-04-23.md.
• Sources:
  • https://developers.uniswap.org/docs/get-started/concepts/how-uniswap-works
  • https://app.uniswap.org/whitepaper.pdf
  • https://app.uniswap.org/whitepaper-v3.pdf
  • https://app.uniswap.org/whitepaper-v4.pdf

Internal linkages

• Best execution-market contrasts: cow-protocol and uniswapx.
• Best concentrated-liquidity descendant worth keeping nearby: bunni.
• Company boundary for the default interface, wallet, and routing-product shell above the contracts: uniswap-labs.
• Keep this note on the AMM baseline job. It does not need to validate every downstream gauge market, router wrapper, or managed-liquidity variant.

Protocol / company boundary

• Keep projects/uniswap on the pool engine itself: invariant logic, LP accounting, and permissionless market creation.
• Use uniswap-labs when the sharper question is who packages the main web app, wallet, and first-party execution surfaces users meet before they ever reason about the contracts directly.
• That split matters because the protocol can stay neutral and immutable while the default access path above it remains company-shaped.

Control surface

• The protocol itself is the pool engine: invariant logic, LP accounting, and permissionless market creation are all legible in the contracts.

• The practical user path still depends on wallets, routers, interfaces, and aggregators, which is why later systems like UniswapX matter mostly as layers that capture routing and execution rights above the pool.

• That interface-and-routing shell is also why uniswap-labs matters separately: a large share of real usage still arrives through company-packaged entry points rather than through raw contract calls.

• The useful comparison lens is simple: if a newer trading system is not changing the AMM itself, it is probably moving leverage into route selection, order admission, filler access, or other layers above the Uniswap pool baseline.

• Last reviewed: 2026-08-13 UTC