Security-Council threshold reduction (RT)
Beefy Finance's assessment for RD-F-182 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Batch-24 Cat 6B RT signal (T-09 v1.1 candidate). Threshold: Security-Council-equivalent multisig threshold reduction (e.g., 3-of-6 to 2-of-6) or timelock removal within 14 days. Beefy dev multisig current state: 3-of-6 (confirmed per data-cache safe_multisigs[1] threshold=3, owner_count=6; verified against docs.beefy.finance/safety/contracts-and-timelocks). Treasury multisig: 4-of-7. No threshold reduction event detected on any of the six Safe instances (Ethereum dev, Ethereum treasury, Arbitrum, BSC, Optimism, Base, Polygon) at assessment date. Beefy has no protocol-level timelock (timelock_address: null), so any future threshold reduction would be uninhibited in effect — this makes the signal especially load-bearing for Beefy. Drift precedent (3/5 to 2/5 reduction + timelock removal 6 days before $285M exploit) is the reference case. Current posture: stable; no reduction observed.
Sources #
- DocsBeefy Contracts and TimelocksBeefy docs — 3/6 dev multisig, 4/7 treasury, no standalone timelockretrieved 2026-05-16
- Beefy Dev Governance Safe — EtherscanBeefy Dev Multisig — 0x34fEf5DA92c59d6ac21d0a75ce90b351D0Fb6CE6retrieved 2026-05-16
- Beefy data cache — Safe multisig thresholds00-data-cache.json — safe_multisigs[1]: threshold=3, owner_count=6 (dev multisig); safe_multisigs[0]: threshold=4, owner_count=7 (treasury)retrieved 2026-05-16
Methodology #
Detect in real-time whether the bridge/protocol Security Council multisig executes a threshold reduction (e.g. 3/5 → 2/5), timelock removal, or new-signer addition within ≤14 days of either of those events.
See the full factor methodology and distribution across all protocols →