Deployer address prior on-chain history
M^0'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 0xf2f1acbe0ba726fee8d75f3e32900526874740bb is labeled 'M0: Deployer' on Etherscan. 659 total transactions, multichain activity consistent with a dedicated protocol deployer (SetSupportedBridges, SendRegistrar, bridge configuration calls). No hacksdatabase entry for M0 as a rug deployer. No prior rug-linked protocol in transaction history. Activity history is that of a legitimate protocol deployer since 2024.
Sources #
- InternalM^0 Protocol Profile §6 Governance Topology00-profile.md §6 — deployer EOA confirmed as 0xf2f1acbe0ba726fee8d75f3e32900526874740bb with M0: Deployer labelretrieved 2026-05-16
- M0: Deployer — EtherscanM0 Deployer EOA — Etherscan address page with label and transaction historyretrieved 2026-05-16
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 →