Pause activations (trailing 12 months)
Beefy Finance's assessment for RD-F-086 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Beefy has activated its pause/emergency mechanisms multiple times across its history, each in response to upstream threats rather than Beefy malfunctions. In the trailing 12 months (May 2025–May 2026), the Balancer V2 product suspension (November 2024) is within scope. Beefy's vault-level panic() function and dev-multisig-controlled pause are documented in SAFU practices and contracts-and-timelocks docs. The pattern of protective pauses demonstrates a functioning and repeatedly-tested emergency mechanism. Green.
Sources #
- URLPhemex News: Beefy Suspends Balancer V2 Products (2024-11)Balancer V2 suspension November 2024 — Beefy paused all Balancer V2 products defensively within the trailing 12-month windowretrieved 2026-05-16
- Beefy SAFU Practices — safety docsdocs.beefy.finance/safety/beefy-safu-practices — documents 'Panic' mechanism and SAFU-first protocolretrieved 2026-05-16
Methodology #
Count the number of deliberate pause activations with documented reason in the trailing 12 months.
See the full factor methodology and distribution across all protocols →