Security-Council threshold reduction (RT)
Superstate's assessment for RD-F-182 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Batch-24 RT signal (Cat 6B). Trigger: Security Council multisig executes threshold reduction, or timelock removal, or new-signer addition within ≤14 days of either. Superstate has NO Security Council multisig structure: USTB upgrade authority is bare EOA 0xad309BB6f13074128b4F23EF9EA2fe8552AfCA83; USCC upgrade authority is bare EOA 0x8abC89D9b56dFD90dA18e8E18CFaC9111100bDd1. The literal trigger (SC threshold reduction event) cannot fire — no SC exists. However, the underlying risk is MORE severe than the batch-24 trigger pattern (EOA with no wrapper vs 2/5 SC reduction). The protocol is permanently in the 'no gate' state rather than the 'reduced gate' state that motivated F182. Scored yellow: underlying control-weakening risk class is present at maximum severity; literal trigger does not apply. Cross-reference RD-F-102 for the same structural finding.
Sources #
- InternalSuperstate data cache and profile — no timelock, no multisig00-data-cache.json: timelock_address = null, safe_addresses: []; 00-profile.md §6: no timelock found, no Gnosis Safe found by Safe APIretrieved 2026-05-16
- USTB proxy upgrade — confirms bare EOA authorityUSTB upgrade tx 0x3396a409... from EOA 0xad309BB6f13074128b4F23EF9EA2fe8552AfCA83 — confirms bare-EOA upgrade authority, no multisig wrapperretrieved 2026-05-16
- USCC proxy upgrade — confirms bare EOA authorityUSCC upgrade tx 0x332573ca... from EOA 0x8abC89D9b56dFD90dA18e8E18CFaC9111100bDd1 — confirms bare-EOA upgrade authority for USCCretrieved 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 →