Emergency-veto multisig present
Beefy Finance's assessment for RD-F-040 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No documented emergency-veto or governance-guardian multisig distinct from the dev multisig. The dev multisig serves as both proposer and executor. No separate guardian contract or emergency-pause DAO found. The keeper role in strategy contracts can panic/pause but is appointed by the dev multisig itself.
Sources #
- DocsBeefy Contracts and Timelocks DocumentationNo dedicated veto multisig documented; dev multisig controls all privileged functionsretrieved 2026-05-16
- Beefy SAFU Standards DocumentationSAFU practices: panic function callable by keeper (set by manager); no independent veto bodyretrieved 2026-05-16
Methodology #
Determine whether an emergency-veto or guardian multisig exists with power to cancel malicious proposals before execution.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol beefy factor RD-F-040 score yellow collected_at 2026-05-16 13:10:30