Security-Council threshold reduction (RT)
Save (formerly Solend)'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 #
Security-Council threshold reduction event (RD-F-182, batch-24, Cat 6B). Applicable to Save's Squads multisigs. Treasury Squads v3 (vault EaFPY9LTQeFR7SEyfbKKFuVMtYvUBbYiiK7WvBJJ7iBU, verified 4-of-6 threshold, on-chain trace sig yGHQUjgk…) and LM Squads v4 (vault 5QbRL9MU5QakL5Fx2He9YaiUzB3TQpVAUBR2ARKN1NrM, verified 2-of-4 threshold, on-chain trace sig yC5opWtg…). No threshold reduction event detected in available on-chain data. No new-signer addition events within 14 days detected. Structural caveat: the program upgrade path is a bare single-EOA (RY93CZYe5g6drtG7W9PmHRPzaBLZ1uwihTzayQTmJfh, is_on_curve: True) — NOT a Security Council multisig. F182 cannot fire on the most critical control surface because there is no multisig threshold to reduce on the program upgrade path. Signal scope is limited to treasury/LM Squads multisigs only.
Sources #
- InternalSave data cache — Treasury Squads v3 multisig verified.research/protocols/save/00-data-cache.json — solana_multisigs[1]: Treasury Squads v3, threshold 4-of-6, vault EaFPY9LTQ...; trace_sig yGHQUjgk...retrieved 2026-05-17
- Save protocol profile — single-EOA upgrade authority caveat.research/protocols/save/00-profile.md §6 — single-key EOA RY93CZYe is upgrade_authority; NOT controlled by either Squads multisigretrieved 2026-05-17
- Save data cache — LM Squads v4 multisig verified.research/protocols/save/00-data-cache.json — solana_multisigs[2]: LM Squads v4, threshold 2-of-4, vault 5QbRL9MU...; trace_sig yC5opWtg...retrieved 2026-05-17
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 →