External keeper/relayer not redundant
Uniswap (v2 + v3)'s assessment for RD-F-062 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No keeper or relayer dependency in V2 or V3 core. All operations (swap, mint, burn, liquidity management, collect) are fully permissionless synchronous user operations. No Chainlink Automation, Gelato, or custom keeper required for core protocol function. V3Staker is an optional peripheral incentive contract whose failure does not impair core pool swapping.
Detail #
V2 and V3 core swap operations are caller-initiated and permissionless. V3Staker (0xe34139463bA50bD61336E0c446Bd8C0867c6fE65) requires manual stakeToken calls from LPs but this is an opt-in peripheral incentive contract. No keeper call in any V2 pair or V3 pool core operation.
Sources #
- DocsUniswap V3 — Security concepts (permissionless operations)Uniswap V3 design: protocol operations are permissionless; no keeper required for core pool function. V2 design: same permissionless model.retrieved 2026-05-12
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →