Breakage analysis per dependency
dYdX v4 (dYdX Chain)'s assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Breakage analysis by dependency: (1) Slinky fails: liquidation engine (GetPerpetualAndMarketPriceAndLiquidityTier in liquidations.go) loses accurate prices; conditional order triggers (stop-limit, take-profit) use stale prices; collateral checks degrade. Missed or premature liquidations possible. (2) Noble IBC fails: USDC inflow blocked; existing balances and positions safe. (3) CEX API failures below minimum exchange count: that market's price treated as invalid. (4) Skip market-mapper fails: new market listings require 4-day governance vote instead. Slinky failure is highest-severity dependency failure mode.
Sources #
- GitHubliquidations.go — dYdX v4-chain x/clobliquidations.go: GetPerpetualAndMarketPriceAndLiquidityTier — oracle price used for liquidation collateral checksretrieved 2026-05-17
- Oracle Prices on dYdX Chain — Help CenterHelp center: oracle prices used for collateralization verification, liquidation triggers, and conditional ordersretrieved 2026-05-17
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 →