ENS/NameStone identity bound to deployer
Fluid'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 #
Fluid deployer 0x0Ed35B... has no ENS name bound. INST deployer 0xf6839... has no ENS name. ENS binding to deployer EOA is not standard Instadapp practice. The FLUID token contract is labeled 'Fluid.io: FLUID Token' on Etherscan but this is a contract verification tag, not an ENS/NameStone binding to the deployer EOA. Factor not applicable to this team's operational practice.
Sources #
- EtherscanFluid protocol deployer address — Etherscanetherscan.io/address/0x0Ed35B1609ec45C7079E80d11149a52717e4859Aretrieved 2026-04-29
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 fluid factor RD-F-117 score gray collected_at 2026-04-29 10:35:01