Chainlink aggregator min/max bound misconfig
Axelar Network'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 #
Axelar's gateway contracts do not consume Chainlink aggregator output for value-securing decisions. The 19 Chainlink feeds in the data cache are peripheral (integrator-side). Chainlink min/max bound misconfiguration is not a risk surface for Axelar's own contracts.
Sources #
- GitHubAxelarGateway.sol sourceAxelarGateway.sol — no Chainlink aggregator interface imported or calledretrieved 2026-05-17
- Axelar data cache oracle_feeds.research/protocols/axelar/00-data-cache.json oracle_feeds array — 19 Chainlink feeds present but confirmed peripheral/integrator-side, not consumed by Axelar core contractsretrieved 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 axelar factor RD-F-060 score green collected_at 2026-05-16 21:57:49