Hot-patch deploys without timelock (last 30 days)
Kinetiq's assessment for RD-F-138 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
The April 7 2026 upgrade of 5 contracts was executed via Safe execTransaction with no timelock route. This is a hot-patch pattern — the entire upgrade from signing to execution was a single Safe tx with no declared delay. No OZ TimelockController exists in the protocol. All upgrades in the last 30 days (the batch) bypassed a timelock by construction.
Sources #
- TxHot-patch upgrade via Safe (no timelock)tx 0xe0d05afb... Safe execTransaction upgrading 5 contracts — no timelock in call path; timelock_address=null confirmedretrieved 2026-05-17
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 →
rubric_version v1.7.0 protocol kinetiq factor RD-F-138 score red collected_at 2026-05-17 15:29:57