Bridge rate-limiter / chain-pause as positive mitigant
Kinetiq's assessment for RD-F-185 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
PauserRegistry (0xac03CABA...) provides emergency pause for EVM contract operations — a positive mitigant. FAQ confirms 'Emergency pause functionality' as a security feature. However, no per-window outflow rate-limiter at protocol level ('None at the protocol level' per FAQ). Hyperliquid L1 chain-pause exists as a theoretical control but is not under Kinetiq's control — it is a platform-governance mechanism. Partial positive mitigant: protocol-level pause exists, but no rate-limiter and L1 pause is not protocol-controlled.
Sources #
- EtherscanKinetiq PauserRegistry 2 on HyperEVMScanPauserRegistry 0xac03CABA51e17c86c921E1f6CBFBdC91F8BB2E6b — emergency pause contractretrieved 2026-05-17
- Kinetiq FAQ — emergency pause and rate limitsKinetiq FAQ: 'Emergency pause functionality' listed; 'None at the protocol level' for rate limitsretrieved 2026-05-17
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 →