Breakage analysis per dependency

Evidence summary #

Partial breakage analysis documented. GMX known-issues page covers: (1) sequencer downtime → keeper must manually pause; (2) keeper failure → orders not executed; (3) oracle outage → orders execute at stale prices or fail. Full formalized dependency-risk document with per-function impact classification does not appear to exist as a standalone publication. Major dependencies are covered in docs.

Detail #

GMX docs known-issues (https://docs.gmx.io/docs/api/contracts/known-issues/) documents multiple failure scenarios. Profile §11 anomaly list covers Chainlink Data Streams centralization risk. Template: yellow = partial analysis, major deps covered.

Sources #

Methodology #

Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.

See the full factor methodology and distribution across all protocols →