ENS/NameStone identity bound to deployer
Yearn Finance'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 #
Yearn uses ENS extensively at the protocol level: ychad.eth (governance multisig 0xFEB4acf3df3cDEA7399794D0869ef76A6EfAff52), brain.ychad.eth, dev.ychad.eth, veyfi.eth (Snapshot space). banteg self-attested use of yfi.banteg.eth as a personal signer address (X post 2020). However, the operative V3 VaultFactory deployer EOA (0x78d4BDEBc0B4140f01BAB63085F94A5a7A1294f2) does not show an ENS reverse-resolution name on Etherscan. Yellow: ENS names bound to governance multisig and key contributor handle but not confirmed on operative deployer EOA.
Sources #
- Etherscan0x78d4BDEBc0B4140f01BAB63085F94A5a7A1294f2 — EtherscanEtherscan — V3 deployer (0x78d4BDEB...) page shows no ENS name in reverse lookupretrieved 2026-05-16
- banteg on X — yfi.banteg.eth attestationbanteg X post — self-attests yfi.banteg.eth as personal signer/delegate addressretrieved 2026-05-16
- Core Yearn Contract Addresses | Yearn DocsYearn core contracts docs — ychad.eth and related ENS names listedretrieved 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 →