Security-Council threshold reduction (RT)
PancakeSwap'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 #
Batch-24 signal (T-09 v1.1 candidate pending FP-rate review). PancakeSwap does not have a formal Security Council structure analogous to Drift Protocol. The nearest analog is the admin Timelock (~6-hour delay, below peer norm) and team multisig. No threshold reduction event detected in public sources. The pre-existing ~6-hour Timelock delay is a static Cat 2 concern (RD-F-032), not a triggered RD-F-182 event. Current multisig signer composition unconfirmed — monitoring infrastructure not deployable without confirmed admin addresses.
Sources #
- EtherscanPancakeSwap Timelock — BscScan (delay: 21,700 seconds / ~6 hours)BscScan Timelock contractretrieved 2026-04-28
- RD-F-182 batch-24: Security-Council threshold reduction RT signalTaxonomy batch-24 RD-F-182 definitionretrieved 2026-04-28
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 →