Security-Council threshold reduction (RT)
Axelar Network'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 #
T-09 v1.1 candidate signal (not yet production-live). Security-Council threshold reduction signal. Applicable: Axelar's custom 3-of-6 EVM Multisig (0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68) is the EVM gateway operator council. Any threshold reduction (3-of-6 to 2-of-6) or new-signer addition within 14 days of a threshold change would trigger. Directly analogous to Drift Apr 2026 pattern (3/5 to 2/5 + timelock removal preceding $285M DPRK exploit). Current posture: multisig last transacted 2026-01-04 (executeContract x3); threshold remains 3-of-6; no signer-change or threshold-reduction event detected in the trailing 14-day window. Signal would NOT fire today.
Sources #
- InternalAxelar protocol profile §6 — governance topology00-profile.md §6 — multisig signers enumerated; 3-of-6 threshold confirmed from Etherscan constructor parametersretrieved 2026-05-17
- Axelar Multisig — EtherscanCustom Multisig 0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68 — threshold 3-of-6, last tx 2026-01-04, no threshold-reduction event detectedretrieved 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 →