Bridge rate-limiter / chain-pause as positive mitigant
Lombard Finance's assessment for RD-F-185 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
BridgeV2 implements per-token/per-chain rate limiting via rateLimit mapping and setTokenRateLimits() function. Hexagate-based automated monitoring provides 24/7 emergency pause capability. LayerZero routes proactively paused in April 2026 following KelpDAO exploit, demonstrating active use of route-level pause as a protective measure.
Sources #
- GitHubhttps://github.com/lombard-finance/evm-smart-contracts/blob/main/contracts/bridge/BridgeV2.solretrieved 2026-05-05
- https://docs.lombard.finance/use/bridgingretrieved 2026-05-05
- https://www.lombard.finance/blog/lbtc-security-and-transparency/retrieved 2026-05-05
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 →
rubric_version v1.7.0 protocol lombard factor RD-F-185 score green collected_at 2026-05-05 12:03:08