ENS/NameStone identity bound to deployer
SUNSwap (sun.io)'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 #
TRON blockchain has no ENS registry or NameStone equivalent. Base58-encoded TRON addresses do not support ENS-style name resolution. TronScan supports address tagging but no public ENS-equivalent name is bound to any deployer address. Factor is structurally not applicable on the TRON non-EVM substrate.
Sources #
- Curator noteTRON substrate not_applicable for ENSTRON substrate has no ENS registry; factor definition requires ENS/NameStone bound identity which is EVM-specific. Per profile §1 (TRON-native, non-EVM, base58 addresses).retrieved 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 sunswap factor RD-F-117 score not_applicable collected_at 2026-05-17 14:37:31