Hot-patch deploys without timelock (last 30 days)

GMX v2 (GMX Synthetics)'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 #

Hot-patch deploys without timelock in last 30 days cannot be assessed. Re-deploy model means no Upgraded events to track; new contract deploys at new addresses are the upgrade mechanism. Arbiscan deploy event history unavailable (403). No confirmed hot-patches from public sources.

Sources #

Curator note
Hot-patch scan unavailableArbiscan 403 prevents deploy event scan. Re-deploy model: look for new ExchangeRouter/handler addresses in last 30 days — not verifiable without explorer access.retrieved 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 gmx-v2 factor RD-F-138 score gray collected_at 2026-05-05 11:15:06