ENS/NameStone identity bound to deployer
Circle USYC'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 or NameStone identity is bound to deployer EOA 0xb2b98e8672d4aad438f6ffec581cfe6f745496ff. Etherscan displays the address with the 'Hashnote: Deployer' label (Etherscan's own system label, not an on-chain ENS binding). For a fully-doxxed corporate entity this is not an identity-risk concern, but the factor definition requires checking the ENS binding specifically. Factor is yellow because the deployer lacks an ENS name - mitigation is that identity is established through many other verifiable means.
Sources #
- EtherscanHashnote: Deployer - Etherscan - no ENS bindingEtherscan deployer address page showing 'Hashnote: Deployer' system label but no ENS name bindingretrieved 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 →