Bridge rate-limiter / chain-pause as positive mitigant
Uniswap (v2 + v3)'s assessment for RD-F-185 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Not applicable. Uniswap V2 and V3 are DEX protocols, not bridges. No outflow rate-limiter and no chain-pause mechanism is applicable. Profile meta: has_bridge_surface=false, is_a_bridge=false. Data cache: layerzero.present=false.
Detail #
F185 is defined as a positive mitigant for bridge protocols: 'does the bridge implement a per-window outflow rate-limiter? Does the underlying chain have an emergency-pause capability that the protocol team can trigger?' Uniswap V2 and V3 are spot DEXes — not bridges. There is no bridge TVL, no bridge validator set, no cross-chain message-passing operated by Uniswap. Each chain deployment is an independent factory/router with no cross-chain communication. UNI token bridging uses canonical L2 bridges operated by L2s (Arbitrum, Optimism, Base, Polygon canonical bridges), not by Uniswap. LayerZero: data cache layerzero.present=false. Not applicable.
Sources #
- Curator noteUniswap profile meta and data cacheProfile meta: has_bridge_surface=false, is_a_bridge=false; layerzero.present=falseretrieved 2026-05-12
Methodology #
Determine whether the bridge implements a per-window outflow rate-limiter (and at what cap), and whether the protocol team can trigger a chain-level or validator-set emergency pause.
See the full factor methodology and distribution across all protocols →