ENS/NameStone identity bound to deployer
Falcon 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 #
Deployer `0x804016c31e52805eb00e0Ef42126Fd3e980A0b33` has no ENS name or NameStone reverse-resolution name. Etherscan shows only the protocol-level label 'Falcon Finance: Deployer' which provides functional identification equivalence but does not satisfy the ENS/NameStone-specific criterion. Yellow reflects absence of the specific mechanism.
Detail #
Etherscan page for the deployer address shows no ENS name in the address header. The label 'Falcon Finance: Deployer' is a centralized Etherscan-attributed tag, not a decentralized ENS binding. Per the factor definition, ENS or NameStone identity binding is the specific requirement; the Etherscan label does not satisfy it.
Sources #
- EtherscanFalcon Finance: Deployer | EtherscanEtherscan deployer — labeled 'Falcon Finance: Deployer', no ENS name displayed in address headerretrieved 2026-05-12
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 →