Dependency graph (protocols depended upon)
GMX v2 (GMX Synthetics)'s assessment for RD-F-050 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Core v2 trading path dependencies: (1) Chainlink Data Streams DON (price signing); (2) Chainlink on-chain AggregatorV3 (deviation reference); (3) ORDER_KEEPER network (order execution); (4) Arbitrum sequencer uptime feed; (5) DataStore (oracle config, immutable in Oracle.sol constructor); (6) RoleStore (access control). No Uniswap/Aave/Curve/external DeFi protocol dependency in core trading path. GMX token contract is peripheral (fee distribution only).
Detail #
Profile §7 confirms no Uniswap/Aave integration. Data cache borrow.present: false. Oracle.sol immutable dependencies: DataStore, EventEmitter, sequencerUptimeFeed. Core dependency graph is well-bounded — primarily Chainlink infrastructure. All dependencies are highly reliable providers with documented SLAs and industry-standard tracks.
Sources #
- GitHubOracle.solOracle.sol — immutable constructor dependencies (DataStore, EventEmitter, sequencerUptimeFeed)retrieved 2026-05-05
- GMX v2 Contract AddressesProfile §7 — no Uniswap/Aave/Curve in core v2 trading pathretrieved 2026-05-05
Methodology #
List all external protocols whose failure would directly impair this protocol (LST providers, bridges, stablecoin issuers, keepers).
See the full factor methodology and distribution across all protocols →