ENS/NameStone identity bound to deployer
Symbiotic's assessment for RD-F-117 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No ENS reverse-record found for either deployer EOA (0x9AbC... or 0xb2cd...) via Etherscan address overview pages. No ENS name visible in address labels. Web search for symbiotic.eth or putyatin.eth returned no results. ENS binding absent. Mitigating factor: both founders are fully named/doxxed at real-name level, so ENS is a corroborative signal, not a substitute. Yellow rather than red given strong real-name identity.
Sources #
- EtherscanEtherscan: 0x9AbC... (no ENS label)Etherscan address page for 0x9AbC... — no ENS label shown in address headerretrieved 2026-05-16
- Etherscan: 0xb2cd... (no ENS label)Etherscan address page for 0xb2cd... — no ENS label shownretrieved 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 →