Security-Council threshold reduction (RT)
Rocket Pool'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 #
Signal applicable: Rocket Pool has a pDAO Security Council introduced in Houston (2024-05-06) with veto powers over protocol upgrades. A threshold reduction (e.g., 3/5 → 2/5) in the SC Safe would match the Drift Protocol pattern (3/5 → 2/5 SC change + timelock removal, 6 days before $285M DPRK exploit). Saturn One introduced mandatory delays with SC veto during delay period. However: (1) SC Safe multisig contract address has not been publicly resolved in the protocol profile — governance-admin-analyst must enumerate from RocketStorage; (2) without the SC address, monitoring cannot be configured. No SC threshold reduction events documented in public data. Signal applicable but cannot be wired without SC address resolution.
Sources #
- URLSaturn One upgrade siteSaturn One upgrade — mandatory delays introduced with Security Council veto power during delay windowretrieved 2026-05-04
- Saturn 1 Timeline — RP Governance ForumSaturn 1 Timeline governance post — pDAO Security Council veto powers during mandatory upgrade delaysretrieved 2026-05-04
- Profile §12 — SC address gapProfile §12 gap flag: pDAO Security Council address not surfaced — governance-admin-analyst must enumerate via RocketStorage lookupretrieved 2026-05-04
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 →