Fork has different economic parameters than upstream
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-132 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
v2: protocol fee mechanic added (feeToSetter role, SushiMaker fee conversion). PeckShield audit reviewed these additions. v3: Sushi-specific fee tiers (0.01%, 0.05%, 1%) differ from Uniswap v3 defaults. No explicit delta-audit confirms the Sushi v3 fee tier parameters are safe. The RouteProcessor series adds economic parameters (routing fees, callback logic) without fresh audit of all parameter choices. Scoring yellow: parameter deviations exist without full re-audit for v3-specific configuration.
Sources #
- AuditPeckShield-Audit-Report-SushiSwap-v1.0.pdfPeckShield v2 audit — reviewed SushiMaker fee conversion mechanism; coverage for v2 fee parameter deltaretrieved 2026-05-17
- SushiV3Factory Etherscan source — fee tier configurationUniswapV3Factory 0xbaceb8ec — enableFeeAmount for 3 tiers; Sushi-specific configuration vs Uniswap v3 defaultretrieved 2026-05-17
Methodology #
Determine whether the fork's economic parameters (collateral factor, LTV, fee structure) differ from upstream audited defaults without a subsequent re-audit.
See the full factor methodology and distribution across all protocols →