ENS/NameStone identity bound to deployer
Usual (USD0 / bUSD0 / USUAL)'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 name is directly bound to deployer EOA `0xab175f3ed4e9e021fa491ae12c7a08d85b27feef`. The Gnosis Safe that funded the deployer (0x34DC124e0ea6e0cdac7605ec3c5153dca17b6ba1) was created by moul.eth — establishing an ENS-associated entity 2 hops from the deployer, but no direct ENS binding on the deployer itself. Factor definition requires ENS bound to the deployer address; partial credit via 2-hop association but not directly satisfied. Yellow rather than red because the indirect ENS association via moul.eth implies a real-identity anchor at 2-hop; yellow rather than green because the direct deployer has no ENS.
Sources #
- EtherscanFunding Safe (moul.eth-created) — EtherscanFunding Gnosis Safe 0x34DC124 — Etherscan page notes created by moul.eth (ENS holder)retrieved 2026-05-17
- Usual: Deployer — Etherscan (ENS check)Deployer EOA Etherscan page — no ENS name tag displayed on deployer addressretrieved 2026-05-17
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 →