Unusual mempool pattern from deployer wallet

Evidence summary #

Unusual mempool pattern from deployer wallet | Applicable: Partial — v1 deployer inactive since 2020-09-30; v2/v3 deployer address not in data cache | v1 deployer (0x6e9eef9b53a69f37efcab8489706e8b2bd82608b) last active 2020-09-30, no recent mempool activity. V2/v3 deployer addresses not resolved (data cache: deployer.address: null). Signal is not actionable without v2/v3 deployer address registration. No unusual activity from known Balancer admin or relay wallets in assessment window. | Threshold: Deployer wallet submits unusual sequence (new deploys, mass approvals) vs historical baseline | Would fire: No (signal not configured — deployer address unresolved)

Sources #

Methodology #

Detect whether the deployer wallet submits an unusual sequence (new contract deploys, mass approvals) vs its historical baseline.

See the full factor methodology and distribution across all protocols →