ENS/NameStone identity bound to deployer

Orca'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 #

Orca is a Solana-native protocol (non-EVM substrate). ENS (Ethereum Name Service) and NameStone operate exclusively on Ethereum L1 and have no registry, resolver, or deployment on Solana mainnet. There is no architectural path by which a Solana program or keypair can have a bound ENS name. This factor is structurally inapplicable due to substrate incompatibility — not due to data absence.

Sources #

Curator note
Phase 2 briefing U7 pre-mark — ENS not_applicable for non-EVM protocolsBriefing §7 U7 pre-mark: F117 not_applicable, gap_reason not_applicable — Orca is non-EVM, no ENS registry on Solanaretrieved 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 →

rubric_version v1.7.0 protocol orca factor RD-F-117 score not_applicable collected_at 2026-05-16 02:39:16