Deployer address prior on-chain history
Liquity V1 + V2 (LUSD / BOLD)'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 #
V2 deployer (0x83cfa33a2ee969f8add9a2acdcdc0d7e556e5ed0, labeled Liquity V2: Deployer 2): first active May 2024, transactions exclusively Liquity v2 protocol deployments (CollateralRegistry, TroveManagers, StabilityPools) and Create2Factory interactions. A UniV4MerklRewards contract was deployed Dec 2025. Normal developer history pattern with no rug-linked pattern. V1 deployer (0xa850535D3628CD4dFEB528dC85cfA93051Ff2984, labeled Liquity: Deployer): 104 lifetime transactions, all Liquity v1 lockup contracts and system deployments from 2021-2024. Both addresses: categorical classification = normal-dev-history.
Sources #
- EtherscanLiquity: Deployer | Address 0xa850535D3628CD4dFEB528dC85cfA93051Ff2984Etherscan address page for Liquity v1 Deployer showing 104 txs and deployment historyretrieved 2026-05-16
- Liquity V2: Deployer 2 | Address 0x83cfa33a2ee969f8add9a2acdcdc0d7e556e5ed0Etherscan address page for Liquity V2: Deployer 2 showing transaction history and labelretrieved 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 →