Chainlink aggregator min/max bound misconfig
dYdX v4 (dYdX Chain)'s assessment for RD-F-060 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Not applicable — dYdX v4 does not use Chainlink. The validator-reported price model via Slinky has no Chainlink aggregator configuration. Data cache listing Chainlink feeds is a known false positive for Cosmos non-EVM chains (U6 advisory). x/prices module source has no Chainlink imports.
Sources #
- GitHubx/prices module — dYdX v4-chainx/prices module directory: no Chainlink imports or adaptersretrieved 2026-05-17
- 00-profile.md §7 External DependenciesProfile §7: oracle is validator-reported via Slinky, not Chainlink or spot DEX TWAPretrieved 2026-05-17
Methodology #
Determine whether the Chainlink aggregator's `minAnswer` and `maxAnswer` circuit-breaker bounds are misconfigured (too wide or too narrow) for the asset class.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol dydx-v4 factor RD-F-060 score green collected_at 2026-05-17 09:58:47