Deployer address prior on-chain history
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-114 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Legacy v2 deployer 0xf942dba4159cb61f8ad88ca4a83f5204e8f4a6bd: Etherscan-labeled 'SushiSwap: Deployer'; funded by Binance (CEX) ~5y 264d ago; holds 19 ETH, xSUSHI, USDT, USDC — consistent with long-term OG DeFi operator wallet. No prior rug label. Operative v3 deployer 0xf87bc5535602077d340806d71f805ea9907a843d: no Etherscan label; first tx ~Apr 2023; small ETH and misc tokens. No prior rug history on either deployer address. Version asymmetry noted: v2 deployer is Chef Nomi-era (2020); v3 deployer is current-team era (2023). Neither carries rug-linked history.
Sources #
- Etherscanv3 Factory Deployer — EtherscanEtherscan — 0xf87bc5535602077d — v3 factory deployer, no label, small balanceretrieved 2026-05-17
- SushiSwap: Deployer — EtherscanEtherscan — SushiSwap: Deployer 0xf942dba — label, balance, funded by Binanceretrieved 2026-05-17
Methodology #
Classify the deployer address history as: none (fresh address) / normal-dev-history (prior protocol deploys, non-flagged activity) / linked-to-prior-rug (deployer used in prior known rug).
See the full factor methodology and distribution across all protocols →