SushiSwap launched in August 2020 as a direct copy of Uniswap's code. Its creator — an anonymous developer called Chef Nomi — added one thing Uniswap didn't have at the time: a token that paid fees to people who held it. Within weeks, roughly $1 billion in liquidity migrated from Uniswap to SushiSwap in what became known as a "vampire attack" — one of the more memorable events in early DeFi history.
Uniswap responded by launching its own token (UNI) and airdropping it to past users. The liquidity mostly returned.
Today, both protocols are live, both have billions in total value locked, and both are operating AMM-based DEXes. But they've diverged significantly from that shared starting point. The mechanism differences matter — and so does the governance track record.
How Both Protocols Actually Work
Both Uniswap and SushiSwap are Automated Market Makers. Instead of order books, they use liquidity pools: pairs of tokens locked in smart contracts. Prices are determined algorithmically by the ratio of tokens in each pool (the classic x * y = k constant product formula). When you swap, you're trading against that pool — not against a counterparty.
That's the shared foundation. Here's where they've separated.
Uniswap's Version Progression
Uniswap v2 (May 2020) was the baseline SushiSwap forked — ERC-20/ERC-20 pairs, on-chain price oracles, flash swaps.
Uniswap v3 (May 2021) was a meaningful architectural shift. It introduced concentrated liquidity: instead of spreading liquidity uniformly across all possible prices, LPs can specify a price range where their capital is deployed. This makes capital far more efficient — the same amount of liquidity can support much higher trading volume within a tight price band. The tradeoff is active management: LPs outside the current price earn no fees, so positions require monitoring.
Uniswap v4 launched in early 2025. The headline feature is hooks — custom contracts that can execute logic at specific lifecycle points in a pool (before and after swaps, before and after liquidity changes, and others). This turns Uniswap into more of a protocol platform: developers can build custom AMM behavior without forking the whole system. A pool with dynamic fees based on volatility, or one that deposits idle liquidity into a lending protocol, becomes possible via hooks without a new token or governance vote.
Separately, UniswapX (2023) introduced an off-chain, intent-based routing layer. Swappers sign an order expressing what they want; fillers (MEV searchers and market makers) compete to execute it on-chain at the best price. The result is better prices and built-in MEV protection for users, at the cost of introducing off-chain infrastructure into what was a fully on-chain protocol.
SushiSwap's Evolution
SushiSwap kept the v2 architecture as its base for longer. The SUSHI token gave it a different fee structure from day one: 0.25% of every swap goes to LPs, and 0.05% goes to xSUSHI holders (stakers of the SUSHI governance token). This is the meaningful early differentiator — Uniswap's fee switch (protocol fees redirected away from LPs) was proposed for years but only partially activated in 2024, after years of governance debate.
SushiSwap also built adjacent products: BentoBox (a vault that earns yield on idle liquidity), Kashi (an isolated margin lending market built on top of BentoBox), and the Trident AMM framework (designed to support multiple pool types). Trident was positioned as SushiSwap's answer to Uniswap v3's capital efficiency. In practice, its adoption has been limited.
Multi-chain was SushiSwap's most consistent differentiator: the protocol deployed across 30+ chains well before Uniswap's more selective expansion, capturing liquidity in markets where Uniswap wasn't present.
Where Constraints Live
The fundamental constraint for both protocols is the same: a DEX can only be as useful as the liquidity it attracts, and liquidity follows fees, volume, and safety.
For Uniswap, the concentrated liquidity model in v3 creates an LP management burden that favors sophisticated actors. Retail LPs in v3 frequently suffer losses against professional market makers who rebalance continuously. The v4 hooks architecture addresses this over time (pools can automate rebalancing) but introduces a new complexity: hook contracts are third-party code, which means the trust model per pool is now different.
For SushiSwap, the binding constraint has been governance stability. The protocol has cycled through several leadership transitions — Chef Nomi's resignation after selling developer funds in September 2020 (the funds were eventually returned), community-led management under 0xMaki, and a subsequent CEO structure under Jared Grey from late 2022. Each transition created friction and distracted from product development. A protocol's governance credibility is a real competitive input, and SushiSwap's track record here is legitimately mixed.
What's Changing
Uniswap v4's hooks represent the clearest active shift — the protocol is moving from a fixed-curve exchange to an extensible platform. Whether that translates to volume gain or primarily benefits builders of pools depends on whether the ecosystem develops useful hook libraries and whether users actually end up in hook-enabled pools. Early signs (first months post-launch) suggest developer interest is high; it's too early to read adoption.
The fee switch activation in Uniswap v3 (some pools began distributing protocol fees to UNI stakers in 2024) is a live variable: it reduces LP take-home and could incentivize LP migration to protocols without protocol fees if the gap is wide enough.
For SushiSwap, the most relevant active variable is whether multi-chain presence holds value as Uniswap v3 and v4 deploy to more chains. If Uniswap occupies every chain where volume materializes, the geographic moat that SushiSwap built becomes less durable.
What Would Confirm the Current Direction
Uniswap v4 hooks adoption: new pool types gaining non-trivial volume within 12 months would suggest the platform model is working. Uniswap LP TVL remaining stable despite protocol fee reduction would indicate LP demand is inelastic to the small fee change. For SushiSwap, multi-year governance stability and product execution against a stated roadmap would be the meaningful signal.
What Would Break or Invalidate It
A hook contract exploit causing fund loss in a v4 pool would raise serious questions about the hooks model and likely suppress v4 adoption. Uniswap's fee switch triggering significant LP migration to SushiSwap or Curve would reopen the competitive question meaningfully. SushiSwap gaining material concentrated liquidity market share — comparable to v3's efficiency — would change the capital efficiency framing. A credible governance attack on either protocol's treasury or admin keys would be a category-level event.
Timing Perspective
Now: Uniswap dominates Ethereum DEX volume by a wide margin (consistently 50–70% depending on the period). SushiSwap's live differentiators are multi-chain breadth and the xSUSHI fee-sharing model.
Next: Uniswap v4 hooks ecosystem maturation (12–18 months for meaningful pool adoption) and fee switch effects on LP behavior are the active watchpoints.
Later: Whether the modular AMM-as-platform model compounds Uniswap's lead, or whether a newer architecture — fully off-chain intents, account abstraction-native DEXes — displaces on-chain AMMs for retail users.
What This Doesn't Mean
This post explains the mechanism and governance differences between two protocols. It doesn't compare token price performance, recommend one protocol over another, or serve as a guide to providing liquidity. LP decisions involve impermanent loss risk, active management requirements, and tax considerations that are outside this scope.
The protocols are structurally different today despite sharing an origin. The mechanism tells you what's different. Whether that difference matters for any particular use case depends on factors specific to the user.
This is the static explanation. Tracked signal updates and threshold monitoring are part of the Macro Brief, not this post.
