Handle reuse across failed/rugged projects
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-118 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No evidence of handle reuse across failed/rugged projects. Chef Nomi (@0xChefNomi) — same pseudonymous handle throughout SushiSwap; the 2020 dev-fund incident IS the associated conduct under this same handle, not a handle switch. Jared Grey (@jaredgrey) — same real identity used at EONS/ALQO/Bitfineon/SushiSwap; no alias switching to evade prior project associations. 0xMaki — pseudonymous with no documented prior rugged-project alias reuse. No cross-protocol impersonation or handle recycling pattern found.
Sources #
- URLSushiSwap Head Chef Hit by Controversy in First WeekBlockworks 2022 — Jared Grey same real-name identity across EONS/ALQO/Sushiretrieved 2026-05-17
- Chef Nomi — People in cryptoIQ.wiki Chef Nomi — same pseudonymous handle throughoutretrieved 2026-05-17
Methodology #
Determine whether any social handle (Twitter, Discord) has been associated with a prior rugged or failed project under a different alias.
See the full factor methodology and distribution across all protocols →