ENS/NameStone identity bound to deployer
Lista DAO's assessment for RD-F-117 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
BSC EVM substrate. ENS is Ethereum-native. BNS (Binance Name Service / .bnb names via Web3 Name Service) is the BSC analog. No BNS name or ENS-equivalent binding found on deployer 0xd7e38800... or multisig 0x8d388136... per BSCScan fetch. U7 pre-mark applied: substrate is BSC; no ENS-equivalent found. Scoring gray with gap_reason 'not_applicable_substrate' — BSC name services have minimal adoption vs ENS; absence of binding is the expected state for most BSC protocols.
Sources #
- Curator noteU7 pre-mark — BSC ENS analog assessmentU7 pre-mark: BSC substrate; ENS not applicable; BNS adoption minimal; gap_reason: not_applicable_substrateretrieved 2026-05-12
- BSCScan: 0x8d388136d578dCD791D081c6042284CED6d9B0c6 (Admin Multisig)BSCScan address page for admin multisig — no ENS/BNS name binding visibleretrieved 2026-05-12
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 →