ENS/NameStone identity bound to deployer
Rocket Pool'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 #
Deployer 2 (0x0ccf14983364a7735d369879603930afe10df21e) does not have a confirmed bound ENS name. Etherscan shows a public name tag 'Rocket Pool: Deployer 2' providing protocol-affiliation labeling, but this is an Etherscan-applied tag, not an on-chain ENS binding. The 'darcius' GitHub handle is publicly linked to David Rugendyke and the rocket-pool org, but the chain between 'darcius' and the deployer address is not formally on-chain-attested. Weaker identity binding than ENS; scored yellow.
Sources #
- GitHubdarcius GitHub profileGitHub handle 'darcius' publicly associated with David Rugendyke and rocket-pool org — off-chain identity link, not ENS bindingretrieved 2026-05-04
- Rocket Pool: Deployer 2 on EtherscanEtherscan address page shows public name tag 'Rocket Pool: Deployer 2' — Etherscan-applied label, not on-chain ENS bindingretrieved 2026-05-04
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 →