Security-Council threshold reduction (RT)

Evidence summary #

F182 (batch-24, Cat 6B): Security-Council threshold-reduction event signal. Applicable and elevated. Current state: 4-of-7 threshold verified via Safe Transaction Service API (cache: threshold=4, owner_count=7). No ChangedThreshold event detected at assessment date. Posture is yellow because: (1) no timelock exists between a threshold-reduction transaction and its effect — a reduction from 4/7 to 3/7 or 2/7 would complete instantaneously within a single Safe execution, replicating the Drift Protocol 3/5→2/5 precursor pattern; (2) F182 signal suppression requires a matching Snapshot proposal in the preceding window, but the SafeSnap → Safe pathway has no on-chain queue where suppression can be verified before execution; (3) the 2025-11-03 emergency action demonstrated willingness to execute without on-chain pre-announcement, establishing that the Safe can and will act unilaterally. No current threshold change is detected, but structural posture is elevated relative to protocols with an

Sources #

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 →