Bridge signer-set change proposed/executed
Uniswap (v2 + v3)'s assessment for RD-F-103 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2+V3 combined structural N/A. Uniswap V2 and V3 do not operate any cross-chain bridge. Multi-chain deployments are independent factory/router deployments on each chain with no cross-chain message-passing. LayerZero: not present (data cache: layerzero.present: false). UNI token canonical bridges are operated by L2 networks, not Uniswap. No signer set to monitor.
Detail #
Signal fires when any SignerAdded/SignerRemoved/ThresholdChanged event (or bridge-equivalent) occurs AND no matching governance pre-announcement exists in the preceding 24h. For Uniswap: no bridge contract exists to monitor. Each chain deployment (Ethereum, Base, Arbitrum, BSC, Polygon, Optimism) is a fully independent deployment of the same factory/router bytecode with no cross-chain coordination. UNI token bridging uses canonical L2 bridges (Arbitrum Bridge, Optimism Gateway, Base Bridge, Polygon PoS Bridge) — operated by the respective L2 networks, not by Uniswap Labs. Data cache: layerzero.present: false. N/A confirmed.
Sources #
- Curator noteUniswap V2+V3 No Bridge SurfaceData cache: layerzero.present: false; profile §7: no bridges / cross-chain endpoints; each chain deployment fully independentretrieved 2026-05-12
Methodology #
Detect whether a bridge validator or signer-set change has been proposed or executed.
See the full factor methodology and distribution across all protocols →