ENS/NameStone identity bound to deployer

Evidence summary #

No ENS name found bound to either primary deployer (0x8de54b1cefedeab1766b947c7d9a9963436e8fae) or Deployer 1 (0x32a12e3f8b1e1f521bb4fbc47ca473d10d0477de) based on Etherscan display and web OSINT. Deployers are identified via Etherscan public name tags ('Ethena: Deployer') only — not via ENS/NameStone identity binding. Absence of ENS binding is a minor negative signal but not dispositive given the institutional nature of the team and the fact that the deployer addresses are already publicly labeled.

Sources #

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 →