ENS/NameStone identity bound to deployer
Kinetiq'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 #
Deployer EOA 0xb05cb1a8188110ac2cb062996526b43179162509 is HyperEVM-native (chainId 999). ENS (Ethereum Name Service) is an Ethereum L1 infrastructure. The deployer has no confirmed Ethereum L1 presence — it is a HyperEVM-native wallet. While the ENS app shows some interaction when queried with this address, the specific ENS name is not surfaced, and critically, an ENS name bound on Ethereum L1 resolves to an Ethereum L1 address which is a different address space from HyperEVM. This is not the hard TRON/Solana substrate-N/A case, but ENS identity binding genuinely does not apply to a HyperEVM-only deployer in the same way it applies to an Ethereum L1 deployer. Score: not_applicable with rationale.
Sources #
- EtherscanKinetiq Deployer — HyperEVMScanHyperEVMScan deployer page — address is HyperEVM-native (chainId 999); no Ethereum mainnet presence detectedretrieved 2026-05-17
- Kinetiq contracts and auditsProfile §3 confirming all contracts on HyperEVM chainId 999; no Ethereum L1 deploymentretrieved 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 →