ENS/NameStone identity bound to deployer
Beefy Finance'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 #
ENS binding on the protocol deployer (0x4fED5491...) is inconclusive from available tools — ENS domain lookup page references the address but the actual reverse record name could not be confirmed. One core contributor (Jack Gale) has strong ENS binding: jackgale.eth resolves to a verifiable public identity (GitHub bio, LinkedIn, Mirror.xyz) — but Jack Gale is a contributor, not the protocol deployer. The protocol deployer itself does not have a publicly confirmed ENS reverse record linking to a verifiable identity based on available OSINT evidence. Score: Yellow — partial ENS binding at contributor level; deployer ENS binding not confirmed.
Sources #
- URLENS lookup for Beefy Deployerapp.ens.domains/0x4fed5491693007f0cd49f4614ffc38ab6a04b619 — address referenced but reverse record name not confirmed in page contentretrieved 2026-05-16
- iamjackgale GitHub Profile (jackgale.eth)github.com/iamjackgale — bio shows jackgale.eth as ENS handle with verifiable identityretrieved 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 →