Security-Council threshold reduction (RT)
JustLend DAO'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 #
Security-Council threshold reduction event (batch-24 RT signal, Cat 6B) — T-09 v1.1 candidate, not production-live. Applicable conditionally: JustLend has GovernorBravo + Timelock governance. The Drift Protocol precursor pattern (3/5→2/5 SC multisig threshold reduction + timelock removal, 6 days before DPRK exploit) is the signal's reference event. Whether JustLend has a Security Council-style multisig with an admin() role on Timelock TRWNvb15NmfNKNLhQpxefFz7cNjrYjEw7x or Unitroller TGjYzgCyPobsNS9n6WcbdLVR9dH7mWqFx7 is unresolved — data cache deployer.address = null, governance.type = 'unknown'. No threshold-reduction event detected from public governance forum or proposal history. Requires Tronscan curator read of admin() on both contracts before this signal can be calibrated. This is a T-09 v1.1 candidate signal not in the production v1 shortlist.
Sources #
- Curator noteCurator assessment — admin path unresolved on TRONData cache governance.type = 'unknown'; deployer.address = null. Admin() on Timelock and Unitroller must be read on Tronscan by curator before RD-F-182 can be calibrated. This blocks assessment.retrieved 2026-05-17
- JustLend DAO — Deployed Contracts DocumentationJustLend DAO deployed contracts — Timelock TRWNvb15NmfNKNLhQpxefFz7cNjrYjEw7x; GovernorBravoDelegator TEqiF5JbhDPD77yjEfnEMncGRZNDt2uogD — admin() path unresolved on TRONretrieved 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 →