ENS/NameStone identity bound to deployer
Dolomite's assessment for RD-F-117 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
ENS lookup not mechanically completed (Arbiscan/Etherscan direct address pages return 403 via WebFetch). No ENS binding found in any search result for deployer 0x4427040bBbc8084Acf86ff409e84a83B3FaD9e85 or the 3 Safe signer EOAs. Protocol identity is established via team legal names (Corey Caplan, Adam Knuckey) and Leavitt Innovations LLC, not via ENS-bound deployer addresses. ENS registry not directly queried successfully.
Sources #
- Curator noteENS lookup gap noteENS registry query blocked by 403 on Arbiscan/Etherscan address pages; no ENS binding surfaced in four parallel OSINT search passesretrieved 2026-05-16
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 →