Bridge rate-limiter / chain-pause as positive mitigant
Save (formerly Solend)'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 #
Save does not operate a cross-chain bridge. Solana validators have chain-level pause capability (cluster restarts — known public fact). Solend v2 whitepaper introduced outflow rate limits as a feature; if deployed, this is a positive mitigant, but confirmed deployment status and parameters are not publicly documented. Yellow: Solana chain-level pause exists as network-wide positive mitigant; protocol-level outflow rate limiter mentioned in v2 but parameters unconfirmed.
Sources #
- URLGate.com — Solend v2 features (outflow rate limits mentioned)gate.com/learn — Solend v2 features including outflow rate limits; status of deployment unconfirmedretrieved 2026-05-17
- Save profile — no bridge surface; Solana chain-pause capability.research/protocols/save/00-profile.md §5 (Solana BPF, no Save-operated bridge); Solana cluster restart historical precedent (known public fact)retrieved 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 →