ENS/NameStone identity bound to deployer
BENQI's assessment for RD-F-117 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Neither deployer address (Comptroller: 0x5423819B3b5bb38b0E9E9e59F22f9034e2d8819b; sAVAX: 0xb5d72f3e80aC24A26A164ac86234e693195c7d8b) has an ENS or NameStone binding. Snowtrace shows no ENS resolution for either address. Architectural context: ENS is Ethereum mainnet; BENQI is 100% Avalanche C-Chain — an Avalanche-native deployer has no ENS equivalent by design. No Avalanche-native resolver equivalent (e.g. a .avax name system) found in use. Red per template literal (no ENS/NameStone binding), but this represents an architectural non-applicability for non-mainnet protocols rather than a high-risk insider signal. Residual risk from ENS absence is low given Avalanche-native context.
Sources #
- EtherscanSnowtrace — BENQI sAVAX deployerSnowtrace address page for sAVAX deployer — no ENS resolver or labelretrieved 2026-05-16
- Snowtrace — BENQI Comptroller deployerSnowtrace address page for Comptroller deployer — no ENS resolver or labelretrieved 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 →