Deployer address prior on-chain history
Concrete'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 #
Deployer EOA (0x1fa1c72A48243E7C7D78f4b95D942D96A8d05588) first funded ~Jan 2024; 1,035 total transactions, all administrative (GrantRole, RevokeRole, OwnershipTransfer, contract deployments) consistent with a dedicated protocol deployer. No prior contracts deployed before the Concrete V2 factory. No prior rug-linked protocol found for this address. Etherscan label 'Concrete: Deployer' confirms identity. Note: the deployer EOA is the original deployer; live upgrade authority subsequently passed to a 3-of-5 Gnosis Safe (0xdc29BD10CB9000dffBb5aAcD30606c66f07c866C), verified by code-security and governance-admin specialists via Safe Transaction Service API. The RD-F-114 assessment concerns the deployer address's on-chain history and is unaffected by this admin-authority distinction.
Sources #
- Internal00-data-cache.json sources.deployerData cache deployer section: address 0x1fa1c72a; funded_by 0xf3f362441ed96e1f69bb9b6750e5d13f5e4aaa9c; first_tx_date availableretrieved 2026-05-17
- Concrete: Deployer — EtherscanDeployer EOA — Etherscan address page; 1035 txns; first tx ~Jan 2024; funded by 0xf3f36244; all admin-type interactions in early deployment phaseretrieved 2026-05-17
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 →