Deployer address prior on-chain history
ether.fi's assessment for RD-F-114 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Primary deployer 0xf8a86ea1ac39ec529814c377bd484387d395421e: Etherscan label 'ether.fi: Deployer'; first transaction 2023-07-10; used exclusively for ether.fi contract deployments across Ethereum and Base (BaseScan label 'ether.fi: Deployer 1'). etherfi-deployer.eth (0xfa371b6fdcb18d65e88c4c785d61801e176a9ae7): first activity 2024-03-18; ENS-bound. Both deployer addresses show normal-dev-history pattern. No links to prior rug or scam-labeled contracts on either address.
Sources #
- Etherscanether.fi: Deployer (0xf8a86ea1ac39ec529814c377bd484387d395421e) | EtherscanEtherscan: ether.fi Deployer addressretrieved 2026-04-28
- etherfi-deployer.eth | Address 0xfa371b6fdcb18d65e88c4c785d61801e176a9ae7 | EtherscanEtherscan: etherfi-deployer.eth addressretrieved 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 →