ENS/NameStone identity bound to deployer
Concrete'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 #
Deployer EOA (0x1fa1c72a) has no ENS name registered to it per Etherscan search (no ENS-related events in transaction history; address displays only via Etherscan public name tag 'Concrete: Deployer'). Mirror article uses concretexyz.eth as a Mirror publishing handle, which resolves to the org's publishing address, not the deployer EOA. No ENS binding on the deployer itself.
Sources #
- URLConcrete Protocol Mirror article — concretexyz.eth is org publishing handleMirror article uses concretexyz.eth as publishing handle — not a deployer EOA ENS bindingretrieved 2026-05-17
- Concrete: Deployer — Etherscan (no ENS events)Deployer EOA Etherscan page — no ENS events in transaction history; label is public name tag not ENS reverse recordretrieved 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 concrete factor RD-F-117 score yellow collected_at 2026-05-17 14:36:59