ENS/NameStone identity bound to deployer
StakeWise v3'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 #
Primary v3 deployer address 0x229f53ef905545aa53a721d82dbfe4ced7aff65d has NO ENS name bound — Etherscan shows no .eth domain for this wallet. The protocol founder's personal signer wallet 0x61B01a33 (Safe creator) has ENS 'tsudmi.eth' (Dmitri Tsumak). Two Safe signers have ENS handles (ottodv.eth at 0x7E36F1fF, mopsko.eth at 0xc0c9707B). The deployer address itself — the specific address scored in this factor — is ENS-free. Score yellow per factor definition: deployer does not have bound ENS resolvable to verifiable identity.
Sources #
- EtherscanStakeWise: Deployer 1 — Etherscan (no ENS)Etherscan address 0x229f53ef905545aa53a721d82dbfe4ced7aff65d — no ENS name shown in page headerretrieved 2026-05-16
- tsudmi.eth (Dmitri Tsumak) — Etherscan Safe signer 7Etherscan address 0x61B01a33 shows ENS 'tsudmi.eth' — this is the founder signer wallet, not the v3 deployerretrieved 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 →