Bridge rate-limiter / chain-pause as positive mitigant
Beefy Finance'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 #
Beefy vault operations are chain-local — no cross-chain bridge surface for vault TVL. The panic() function in strategy contracts serves as a vault-level emergency-withdraw mechanism (withdraws from external farm to strategy) but is not a rate-limiter. BIFI xERC-20 bridge uses four external adapters (LayerZero, Axelar, Chainlink CCIP, canonical Optimism bridge) — rate-limiting is governed by upstream bridge providers, not Beefy. No Beefy-specific rate-limiter or chain-pause capability confirmed. Partial credit for panic() as a vault-level emergency mechanism.
Sources #
- GitHubBaseAllToNativeFactoryStrat.sol — panic() emergency functionBaseAllToNativeStrat.sol panic() function — emergency withdraw from external farm to strategy; not a rate-limiterretrieved 2026-05-16
- Beefy Token Bridge DocumentationToken bridge uses LayerZero, Axelar, Chainlink CCIP, and Optimism canonical bridge — rate-limiting by upstream providers onlyretrieved 2026-05-16
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 →