Deployed bytecode reproducibility
Uniswap (v2 + v3)'s assessment for RD-F-145 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2: source verified on Etherscan; Solidity 0.5.16; public GitHub repo (v2-core). V3: source verified on Etherscan (Exact Match); Solidity 0.7.6; hardhat config present; audited from specific pre-launch commits. Build reproducibility well-established for both versions. Combined: green.
Detail #
V2: v2-core GitHub is public (github.com/Uniswap/v2-core); Solidity 0.5.16; source verified on Etherscan. Build reproducibility is feasible from declared settings. V3: v3-core GitHub public; data cache: hardhat_config_present=true, package_json_present=true; Solidity 0.7.6; UniswapV3Factory 'Exact Match' verification on Etherscan. Trail of Bits and ABDK audited from specific pre-launch commits — those same commits are deployed, making bytecode reproducibility inherent.
Sources #
- GitHubUniswap v3-core GitHubv3-core: package.json and hardhat config present; Solidity 0.7.6; source verifiedretrieved 2026-04-29
- UniswapV3Factory verified sourceUniswapV3Factory: 'Exact Match' verification on Etherscanretrieved 2026-04-29
Methodology #
Determine whether anyone can independently reproduce the deployed bytecode from the repo and declared build toolchain.
See the full factor methodology and distribution across all protocols →