Security-Council threshold reduction (RT)
Pendle Finance's assessment for RD-F-182 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Security-Council threshold reduction RT signal (batch-24). Fires when a named Security Council multisig executes threshold reduction or timelock removal within <=14 days. Pendle does not have a named Security Council in its governance architecture. The three Safe multisigs serve treasury/admin/fee functions — none is designated as a Security Council with the specific SC-class powers (threshold + timelock + bridge guardian roles). The Dev Multisig (0xE6F0489...) holds upgrade authority but is not a Security Council. Signal is architecturally inapplicable to Pendle's current structure. The analogous static risk (threshold reduction on Dev Multisig) is assessed under RD-F-031 by governance-admin-analyst.
Sources #
- URLLazarus and Kelp Hack — reference for SC pattern originDrift Protocol Apr 2026 SC 3/5->2/5 + timelock removal pattern — Pendle has no equivalent SC architectureretrieved 2026-04-29
- Pendle Ethereum Deployment JSONPendle deployment JSONs list devMultisig, governance, and treasury Safe addresses — none labeled Security Council. No SC equivalent architecture found.retrieved 2026-04-29
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 →