ENS/NameStone identity bound to deployer
Veda (BoringVault)'s assessment for RD-F-117 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Deployer 0x0463e60c7ce10e57911ab7bd1667eaa21de3e79b has ENS name 'troglobyte.eth' bound and visible on the Etherscan address page. The ENS is resolvable and associated with an ether.fi DeFi community persona. Factor applies normally for all-EVM protocols per scope instruction: 'All-EVM — F117 (ENS) applies normally.' Pseudonymous ENS binding (not real-name) satisfies the letter of the factor (ENS bound to deployer); full real-name linkage is not the F117 requirement.
Sources #
- Etherscan0x0463e60c7ce10e57911ab7bd1667eaa21de3e79b — Etherscan (ENS binding)Etherscan address page shows ENS name troglobyte.eth bound to deployer 0x0463e60c7ce10e57911ab7bd1667eaa21de3e79bretrieved 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 →