Post-mortem published within 30 days
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-082 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
RouteProcessor2 (most recent, most material incident, 2023-04-08): post-mortem published 2023-04-18 = 10 days after exploit. Clearly within 30-day window. MISO/JayPegs 2021: real-time public communications; recovery complete within ~18 hours; formal 30-day post-mortem status not independently confirmed. Kashi 2022: no Sushi-authored post-mortem found — BlockSec external writeup serves as primary. At minimum the RP2 post-mortem (most recent) confirms the within-30-day standard was met.
Sources #
- URLRouteProcessor2 Post Mortem (sushi.com)SushiSwap RouteProcessor2 post-mortem (published 2023-04-18, 10 days post-exploit)retrieved 2026-05-17
Methodology #
Determine whether a public post-mortem was published within 30 days of the most recent incident.
See the full factor methodology and distribution across all protocols →