ENS/NameStone identity bound to deployer
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-117 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No ENS name bound to either protocol deployer. Legacy v2 deployer 0xf942dba: no ENS name resolvable from Etherscan address page. Operative v3 deployer 0xf87bc553: no ENS name bound. SushiSwap governance uses ENS space 'sushigov.eth' (bound to governance, not to deployer identity). Etherscan shows a 'SushiSwap: ENS' contract address (0xa1181481...) which is a protocol-level token/contract, not a deployer ENS binding. No identity-bound ENS on deployer addresses.
Sources #
- EtherscanSushiSwap: Deployer — Etherscan (no ENS binding)Etherscan — 0xf942dba address page — no ENS name shownretrieved 2026-05-17
- v3 Factory Deployer — Etherscan (no ENS binding)Etherscan — 0xf87bc553 address page — no ENS name shownretrieved 2026-05-17
Methodology #
Determine whether the deployer address has a bound ENS or NameStone name resolvable to a verifiable identity.
See the full factor methodology and distribution across all protocols →