ENS/NameStone identity bound to deployer
Venus Protocol's assessment for RD-F-117 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No ENS or NameStone name found bound to the primary deployer address 0x1ca3Ac3686071be692be7f1FBeCd668641476D7e. Venus Protocol is BSC-native (BEP-20 ecosystem); ENS is Ethereum-native. No BSC-equivalent name service binding found. The absence of ENS on a BSC-primary deployer is not a risk signal — it is expected for BSC-native deployments. Gray because the factor is not applicable in the negative sense for BSC-native addresses.
Sources #
- Etherscan
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 →