Hot-patch deploys without timelock (last 30 days)
BENQI's assessment for RD-F-138 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No timelock exists across BENQI's protocol. Every admin parameter change is by definition a hot-patch without timelock. However, this factor specifically counts new contract deploys that bypassed a declared timelock in the last 30 days. With no timelock declared, no upgrades are tracked in a timelock queue. No new contract deploy events confirmed within 30 days. Assessed gray: timelock absence already captured in F032/F033; this factor's bypass-counting mechanics are not assessable without a timelock baseline.
Sources #
- DocsRisks & Audits | BENQIBENQI risks docs — no timelock documented anywhere in the protocolretrieved 2026-05-16
Methodology #
Count upgrades executed in the last 30 days without going through the declared timelock path.
See the full factor methodology and distribution across all protocols →