Bridge rate-limiter / chain-pause as positive mitigant
EigenLayer'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 #
EigenLayer is not a bridge; the F185 bridge rate-limiter is not applicable in its primary definition. The closest analogue is the Pauser Multisig (1-of-7, instant-pause) which provides a circuit-breaker capability without delay. A single authorized signer can halt the entire protocol in an emergency. No on-chain rate-limiter for withdrawals beyond the existing 14-day withdrawal queue (post-slashing launch). Scored yellow: instant-pause exists as positive mitigant but no rate-limiter; withdrawal queue is a delay not a cap.
Sources #
- URLhttps://docs.eigenfoundation.org/protocol-governance/technical-architectureretrieved 2026-04-28
- https://blog.eigencloud.xyz/introducing-slashing/retrieved 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 →