Deployer address prior on-chain history
EigenLayer's assessment for RD-F-114 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Data cache deployer.address is null — the data pipeline did not auto-resolve the specific deployer EOA. Eigen Labs core contracts are labeled 'EigenLayer:' on Etherscan (e.g., DelegationManager at 0x39053D51B77DC0d36036Fc1fCc8Cb819df8Ef37A), consistent with institutional deployment under the Eigen Labs entity. No deployer address linked to a prior rug or failed project identified in OSINT. Institutional VC-backed corporate entity deployment provides accountability backstop. Yellow (not green) because the specific deployer EOA(s) were not positively identified and on-chain history of the deployer wallet(s) was not traced at the individual address level. Curator action required: run contractCreator on Etherscan for DelegationManager to close this gap.
Sources #
- EtherscanDelegationManager Proxy — EtherscanEtherscan label 'EigenLayer: DelegationManager' — institutional deployment indicatorretrieved 2026-04-28
- EigenLayer data cache — deployer address null00-data-cache.json deployer.address: null — pipeline gapretrieved 2026-04-28
Methodology #
Classify the deployer address history as: none (fresh address) / normal-dev-history (prior protocol deploys, non-flagged activity) / linked-to-prior-rug (deployer used in prior known rug).
See the full factor methodology and distribution across all protocols →