Stale-approval exposure on deprecated router
GMX v2 (GMX Synthetics)'s assessment for RD-F-168 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
GMX v2 re-deploy model means that when routers are upgraded, old approved addresses remain active for users who approved them. GMX docs note 'contract addresses change when logic contracts are upgraded' and 'integration updates' required — acknowledging stale approval hygiene gap. No active allowance scan performed; no current count of stale approvals to deprecated router addresses. Known architectural hygiene issue in re-deploy models.
Sources #
- DocsGMX known issues — address change integration requirementdocs.gmx.io/docs/api/contracts/known-issues/ — 'New contract deployments risk pricing discrepancies; address changes require integration updates'retrieved 2026-05-05
Methodology #
Count the number of active user approvals (ERC-20 `allowance`) to deprecated router or protocol contracts.
See the full factor methodology and distribution across all protocols →