Security-Council threshold reduction (RT)
Aave v3'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 #
No Security Council threshold reduction at Aave. Guardian multisigs (Governance Guardian 5-of-9, Granular Guardian 5-of-9) have not undergone threshold reductions or timelock removals. The rsETH incident did not involve Aave governance weakening — it involved a third-party bridge (Kelp rsETH LayerZero OFT) DVN misconfiguration. F182 batch-24 signal (Drift Protocol precedent: 3/5→2/5 SC change + timelock removal 6 days before $285M exploit) is not applicable here.
Sources #
- URLEtherscan: Granular Guardian 0x4457cA11E90f416Cc1D3a8E1cA41C0cdEcC251d4Granular Guardian multisigretrieved 2026-04-27
- Etherscan: Governance Guardian 0xCe52ab41C40575B072A18C9700091Ccbe4A06710Governance Guardian multisigretrieved 2026-04-27
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 →