Admin/upgrade transaction in mempool
GMX v2 (GMX Synthetics)'s assessment for RD-F-102 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No admin/upgrade mempool transaction documented at assessment date. All upgrades require 86400s timelock delay across five timelocks (Timelock Arb 0x7A967D114B8676874FA2cFC1C14F3095C88418Eb, GovTimelockController Arb 0xFBEff82f2DD5E51B8AF34b57cf788b4b09d466F9, ConfigTimelockController Arb 0xC77E6C0ca99E02660A23c00A860Dd5a8912DEaF5, and Avalanche equivalents). Any queued upgrade is observable on-chain for 24 hours before execution. Phase-2 signal — not in production scope. Threshold: pending tx from admin address to protocol contracts with admin-function selector AND no matching queued governance proposal.
Sources #
- GitHubhttps://raw.githubusercontent.com/gmx-io/gmx-synthetics/main/deployments/arbitrum/Timelock.jsonretrieved 2026-05-05
- https://docs.gmx.io/docs/api/contracts/addresses/retrieved 2026-05-05
Methodology #
Detect an admin-role or upgrade transaction appearing in the mempool before confirmation.
See the full factor methodology and distribution across all protocols →