Unusual mempool pattern from deployer wallet
Uniswap (v2 + v3)'s assessment for RD-F-092 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2+V3 combined: Data cache deployer.address = null (pipeline gap). V3 operative deployer = Uniswap Labs (corporate entity); V3 core contracts are immutable post-deploy — deployer has no live privileged role. V2 deployer feeToSetter renounced — also no live privileged role. Signal not actionable for immutable protocol deployers with no live admin role; mempool monitoring not configured.
Detail #
Gray per methodology: (1) signal infrastructure requires mempool monitoring not available in static dry run; (2) even if deployer wallet monitoring were configured, neither V2 nor V3 core deployer can execute privileged admin actions post-deploy due to immutability. V3 periphery contracts (UniversalRouter, Permit2) may have separate ownership — governance-admin-analyst scope, not deployer-wallet scope. Structural data gap: deployer.address = null in data cache; resolved via profile §2/§3 to Uniswap Labs but specific EOA address not in cache.
Sources #
- Curator noteData cache deployer gap — Uniswap combined slugData cache: deployer.address null; V3 operative deployer = Uniswap Labs corporate entity per profile §2retrieved 2026-05-12
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 →