Bridge rate-limiter / chain-pause as positive mitigant
Across Protocol's assessment for RD-F-185 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Bridge rate-limiter / chain-pause | No per-chain or per-route outflow rate-limiter identified in publicly documented SpokePool or HubPool code. The bridge model uses relayer inventory (relayers front capital on destination); outflow on-chain is limited by pool liquidity in HubPool. Admin can `setPaused(bool)` on HubPool (immediate, no timelock) and `pauseDeposits(bool)` / `pauseFills(bool)` on SpokePool (onlyAdmin/crossDomainAdmin, no timelock). These are binary pause functions, not rate-limi...
Sources #
- Curator noteExtracted from 02-governance-admin.md — RD-F-185; no URL citedretrieved 2026-04-28
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 →