ENS/NameStone identity bound to deployer
Jito's assessment for RD-F-117 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
ENS is an Ethereum-specific naming system; Jito is Solana-native. No ENS binding to the JTO DAO upgrade authority address (4ivLcnNLhe4cKdpV9b4jyEmxgbYWFgktHcTyyBvYavsD). Solana Name Service (.sol domains) binding to this address not confirmed from public data. However, team identity is robustly established through non-ENS means (company registration, LinkedIn, press, GitHub). Yellow assigned because deployer address identity is established but no on-chain ENS/SNS name-binding exists. Factor is structurally less applicable to Solana protocols than EVM protocols.
Sources #
- DocsJito GitBook on-chain addresses — no ENS/SNS binding indicatedENS inapplicable to Solana; SNS binding not confirmedretrieved 2026-04-29
- Jito profile §3 — Program addressesProfile §3 — Solana program addressesretrieved 2026-04-29
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 →