FORESHOCK

Protocols

Request coverage

Every protocol here carries a dated score and the share of it backed by independently verified evidence. Where that share is still thin the assessment says so, is marked Low-signal rather than given a risk band, and holds every unevidenced category at the neutral midpoint instead of assuming it safe. Every score and its reasoning are free to read; the underlying dependency, incident and audit records are part of a plan. Each reading here is fixed at the date beside it. Re-scoring never stops, but a changed reading reaches plan holders on the day it changes rather than this page, which is what a plan is for. How a score is built, how to read one, and how the rubric was tested against real exploits are all in the methodology.

Coverage grows three ways: protocols Foreshock selects at its own discretion, protocols requested through the Request coverage button, and sponsored assessments delivered on an agreed timeline. No path has a guaranteed date except sponsorship.

Scores run from 0, the safest reading, to 100, the riskiest, where 50 is the neutral midpoint every unverified category is held at. Red marks a protocol scoring 50 or above, the band called Elevated: worse than neutral on the evidence gathered. Amber marks one below it, called Moderate. The boundary is fixed. It does not move as coverage grows, and it is not fitted to any backtest result.

SushiSwap V3

SushiSwap V3 official site N/A

Multi-Chain

:

  • Evidence: this reading is based on 100% of the scored weight, verified against named sources. Categories without verified data are held at the neutral midpoint at their full weight, never counted as safe.
  • Validation: measured against 1 comparable incident/control in this protocol's TVL, age and category bucket.

Published 2026-09-06. Up-to-date reading and 1 change since for subscribers. See plans

Why this rating
Audit profile10.0
2 audits/contests on record, most recent (ABDK (audit of the upstream Uniswap V3 codebase, inherited via unmodified fork, NOT Sushi-commissioned), 2021-03-23) has unread findings, scored as unknown, not assumed clean.
Code characteristics9.0
Admin key: an unidentified controlling contract (no single key can act alone; its signers and any delay are unverified), open source.
TVL profile5.5
TVL is 76% below this protocol's own peak; TVL change (14%) is within a stable range.
Dependency risk3.0
No bridge or oracle dependencies on record. SushiSwap V3 is an unmodified fork of Uniswap V3 and inherits its architecture: it takes no price from outside, instead providing on-chain TWAP data for external systems to consume.
Show the evidenceConfirmed directly in Sushi's own repo: Oracle.sol's own top comment states it 'Provides price and liquidity data useful for a wide variety of system designs', and IUniswapV3PoolDerivedState.sol's observe() returns time-weighted average tick data. No external oracle or bridge dependency was found in docs.sushi.com or Sushi's own V3 repos.
Governance attack surface2.5
Top 10 holders control 15.73%, adjusted figure may still include pooled custody (untagged exchanges, infrastructure contracts) due to tagging coverage limits; exclusions require positive identification.
Historical incidents2.3
No known own or inherited incidents as of 6 September 2026.
Team factors1.8
Doxxed team, track record: mixed.
Protocol age1.5
1249 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.
Bug bounty1.2
Has a bug bounty program, up to $200 000, hosted on Immunefi.
Assets held (7)

Available with a plan. See pricing.

Dependencies (1)

Available with a plan. See pricing.

Incident history (0)

Available with a plan. See pricing.

Audit history (2)

Available with a plan. See pricing.

Common questions about SushiSwap V3

Foreshock's independent reading of SushiSwap V3 is Moderate risk, 36.8 out of 100, as of 6 September 2026. The largest single contributor to that reading is audit profile: 2 audits/contests on record, most recent (ABDK (audit of the upstream Uniswap V3 codebase, inherited via unmodified fork, NOT Sushi-commissioned), 2021-03-23) has unread findings, scored as unknown, not assumed clean. All nine scored categories are backed by verified evidence. This published reading is fixed at that date. Re-scoring never stops, and when a reading changes it reaches plan holders on the day it changes rather than this page. Foreshock publishes the reading and the reasoning behind it. It is not a verdict on whether to use this protocol, and it is not investment advice.

Is SushiSwap V3 safe?
Foreshock does not answer that as a yes or a no. Its independent reading of SushiSwap V3 is Moderate risk, 36.8 out of 100, as of 6 September 2026, led by audit profile: 2 audits/contests on record, most recent (ABDK (audit of the upstream Uniswap V3 codebase, inherited via unmodified fork, NOT Sushi-commissioned), 2021-03-23) has unread findings, scored as unknown, not assumed clean. The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has SushiSwap V3 been audited?
2 audits/contests on record, most recent (ABDK (audit of the upstream Uniswap V3 codebase, inherited via unmodified fork, NOT Sushi-commissioned), 2021-03-23) has unread findings, scored as unknown, not assumed clean. An audit describes the code at the time it was reviewed. It is not a statement that the protocol is safe today.
Who controls SushiSwap V3?
Admin key: an unidentified controlling contract (no single key can act alone; its signers and any delay are unverified), open source. Top 10 holders control 15.73%, adjusted figure may still include pooled custody (untagged exchanges, infrastructure contracts) due to tagging coverage limits; exclusions require positive identification.
Has SushiSwap V3 been exploited before?
No known own or inherited incidents as of 6 September 2026. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this SushiSwap V3 assessment last updated?
6 September 2026, and that date does not move on its own. A reading published here is fixed when it is published; re-scoring never stops, and a changed reading reaches plan holders on the day it changes rather than this page. Every category carries the date of the evidence behind it.
Also covered on Multi-Chain

This assessment follows Foreshock's published methodology. Exact category weights, scoring rules, thresholds, and aggregation logic are proprietary and not shown here. How to interpret this assessment

This reading will change.

This reading is fixed at the date above it, and it stays there. We keep re-scoring SushiSwap V3 as the evidence moves, a new audit, a changed admin control, an incident, and this page is free to read and always will be. The updated reading is what a plan buys: you are told by email on the day it changes, instead of finding out the next time you happen to look.

Pick one protocol and get a free weekly summary of what changed. Same-day alerts come with a plan.

Monitor this protocolGet told when this changesBrowse every protocol