Contributor tenure at admin-permissioned PR
Uniswap (v2 + v3)'s assessment for RD-F-116 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V3 core contracts are fully immutable — no admin-permissioned code changes possible post-deploy. All core contributors (Adams since 2018, Zinsmeister since ~2018-2019, Salem since ~2019-2020) are long-tenured (5-7+ years). V2 contracts also fully immutable. Governance changes require full 7-day on-chain vote plus 2-day timelock before execution. No short-tenure contributor with privileged access identified.
Detail #
Combined v2+v3 assessment. V2 contracts (factory, pairs) are fully immutable with feeToSetter renounced; no admin-permissioned changes are possible. V3 core contracts (factory, pool implementations) are also fully immutable. The only surface where contributor tenure matters is periphery and governance, where the long-tenured core team (Adams, Zinsmeister, Salem, Toda) hold influence but even governance changes require the complete Compound Bravo process including public forum discussion, 7-day voting, and 2-day timelock.
Sources #
- GitHubContributors to Uniswap/v3-core — GitHubGitHub Uniswap/v3-core contributor graphretrieved 2026-04-29
Methodology #
Measure the number of days contributing to the repo of the author of the most recent admin-permissioned code change.
See the full factor methodology and distribution across all protocols →