ENS/NameStone identity bound to deployer
EigenLayer'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 #
Data cache deployer.address is null — deployer EOA not identified, preventing ENS binding check. Eigen Labs multisig addresses are labeled on Etherscan by role ('EigenLayer: Community Multisig', etc.) but no ENS / NameStone name resolution linking deployer EOA to a verifiable real-world identity is confirmed. Gray (not red) — absence of ENS binding is not a risk indicator for an institutional entity with a high-profile named founder. Green would require positive confirmation of ENS / NameStone binding.
Sources #
- InternalEigenLayer data cache — deployer address null00-data-cache.json deployer.address: null — prerequisite for ENS check not metretrieved 2026-04-28
- EigenLayer: Community Multisig — EtherscanEtherscan Community Multisig label — role-based not identity-basedretrieved 2026-04-28
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 →