Hot-patch deploys without timelock (last 30 days)
Balancer (v2 + v3)'s assessment for RD-F-138 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No timelock exists on the primary admin path (RD-F-032 red). Core contracts are immutable so traditional proxy hot-patches are impossible. Parameter/permission changes by the 6-of-11 multisig execute without timelock. The November 2025 emergency response executed immediate factory disabling and gauge killing without timelock — intentionally as emergency response. Cannot confirm specific parameter changes in last 30 days.
Sources #
- URLBlockSec: In-Depth Analysis Balancer V2 ExploitNov 2025 exploit emergency response timeline — immediate gauge killing without timelockretrieved 2026-05-05
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 balancer factor RD-F-138 score yellow collected_at 2026-05-05 12:41:36