Security-Council threshold reduction (RT)
Veda (BoringVault)'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 #
RD-F-182 (batch-24): Security-Council threshold reduction event. Veda has no formal Security Council multisig at protocol level. Per-vault RolesAuthority owners function as de facto admin authorities. No threshold reduction event (e.g., from a 3/5 to 2/5 Safe threshold, or timelock removal) detected on Veda's LayerZeroTeller or primary vault admin multisigs as of 2026-05-17. LayerZero's own infrastructure threshold raised (3/5 → 7/10) post-KelpDAO — a positive mitigant, not a threshold reduction. Signal would not fire today.
Sources #
- URLLayerZero security changes post-KelpDAO — threshold raised, not loweredLayerZero threshold change is an INCREASE (3/5 → 7/10) post-KelpDAO; not a reduction event per RD-F-182 definitionretrieved 2026-05-17
- Etherscan: Veda LayerZeroTellerLayerZeroTeller 0xe97365b41b340352d3d32ca2c7230330f19a1e73 — no threshold-reduction events in recent transaction historyretrieved 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 →