ENS/NameStone identity bound to deployer

stHYPE (Valantis Labs)'s assessment for RD-F-117 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

HyperEVM does not have an ENS registry or NameStone equivalent. The deployer address 0x20e97805... and all Safe signer addresses operate exclusively on HyperEVM (not Ethereum mainnet). ENS is an Ethereum-mainnet concept; there is no analogous on-chain naming system for HyperEVM that would allow binding a verifiable identity to a deployer address. Per non_evm_substrate: true in coverage_flags.

Sources #

Internal
00-data-cache.json — non_evm_substrate flag00-data-cache.json — coverage_flags.non_evm_substrate: true; HyperEVM does not support ENSretrieved 2026-05-17
URL
stHYPE Contract Addresses | Valantis DocumentationHyperEVM architecture — EVM-compatible L2 on Hyperliquid; no ENS deployment documentedretrieved 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 →

rubric_version v1.7.0 protocol staked-hype factor RD-F-117 score not_applicable collected_at 2026-05-17 13:02:38