Code divergence from upstream (%)
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-129 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
v2: core AMM pair and factory logic near-identical to Uniswap v2 (estimated <10% divergence in core logic; additions are MasterChef, SushiMaker, SUSHI token — separate contracts). v3: SushiSwap v3-core carries Sushi-specific fee tiers, multi-chain deployment config, modified interface names. Estimated 10-25% divergence from Uniswap v3 codebase (concentrated liquidity math identical; routing periphery and multi-chain deployment patterns differ more). Direct git diff not performed (cross-org diff not feasible via WebFetch). Scoring yellow for v3 moderate divergence (higher-risk version per combined-slug rule).
Sources #
- EtherscanSushiV3Factory Etherscan sourceUniswapV3Factory 0xbaceb8ec — 3 fee tiers (0.01%, 0.05%, 1%) vs Uniswap v3 default; Sushi-specific configurationretrieved 2026-05-17
- sushiswap/v3-core GitHubsushiswap/v3-core — fork with BSL 1.1 license; fee tiers and multi-chain config differ from Uniswap v3retrieved 2026-05-17
Methodology #
Measure the percentage of lines changed between this fork's deployed code and the stated upstream codebase at fork point.
See the full factor methodology and distribution across all protocols →