ENS/NameStone identity bound to deployer
OpenEden's assessment for RD-F-117 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Deployer EOA 0x7C699ABc0118e5d0fac0a7f317da79275364C50 has no ENS primary name per Etherscan display (no ENS label shown on the TBILL vault contract page for its creator address). ENS absence is the expected norm for institutional RWA deployers operating via a corporate entity (River Labs Pte Ltd / OpenEden Group) — analogous to circle-usyc, spiko, midas peers. Red per rubric (no ENS/NameStone binding) but low risk-signal in institutional-corporate context; this factor is a structural red, not a behavioural-risk red.
Sources #
- EtherscanOpeneden TBILL Vault — Etherscan (creator field, no ENS shown)TBILL vault v2 Etherscan contract page — no ENS label displayed for creator address 0x7C699ABc...364C50retrieved 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 →