Pause activations (trailing 12 months)
Uniswap (v2 + v3)'s assessment for RD-F-086 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2 core contracts are fully immutable — no pause mechanism by design. V3 core contracts (Pool, Factory) are immutable — no pause mechanism. Methodology: gray = protocol has no pause mechanism (structural N/A). Combined: gray.
Detail #
V2: No pause function exists on UniswapV2Factory or UniswapV2Pair by design. V3: Official docs state 'no party is able to pause the contracts, reverse trade execution, or otherwise change the behavior of the protocol in any way.' V3 Pool (UniswapV3Pool.sol) contains no Paused event or pause() function. Periphery contracts (UniversalRouter, Permit2) may have separate emergency controls, but no pause event on these has been publicly documented in the trailing 12 months (May 2025–May 2026). Score: gray (structural N/A for immutable core).
Sources #
- GitHubUniswapV3Pool source — no pause functionv3-core UniswapV3Pool.sol — no Paused event or pause functionretrieved 2026-05-12
- The Uniswap Protocol — no pause mechanismUniswap protocol immutability documentationretrieved 2026-04-29
Methodology #
Count the number of deliberate pause activations with documented reason in the trailing 12 months.
See the full factor methodology and distribution across all protocols →