Test-mode parameters in deploy
Uniswap (v2 + v3)'s assessment for RD-F-141 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2: no test-mode artifacts; dapp.org audit confirmed production readiness; feeToSetter renounced as designed. V3: no test-mode parameters; Factory deployed with Timelock as owner; ABDK audit confirmed production readiness (159 minor issues all resolved pre-launch). Combined: green.
Detail #
V2: dapp.org audit (2020) confirmed v2-core production readiness. feeToSetter was set to a Uniswap Labs address at launch then renounced — this was by design, not a test artifact. V3: ABDK audit confirmed 159 minor issues all resolved before launch. Factory deployed with Timelock as owner (correct production config). No test oracle addresses, infinite allowances, or test-mode configs found in production deployment. Compiler settings (Solidity 0.7.6, optimizer enabled) are consistent with production deployment.
Sources #
- AuditABDK audit reportABDK audit: 159 minor issues, all resolved pre-launch; no test-mode paramsretrieved 2026-04-29
- UniswapV3Factory verified sourceFactory: Solidity 0.7.6, production Timelock owner, verified production sourceretrieved 2026-04-29
Methodology #
Determine whether the deployed configuration retains test-mode parameters (test oracle address, infinite allowance, admin = deployer EOA).
See the full factor methodology and distribution across all protocols →