Oracle staleness check present
Axelar Network's assessment for RD-F-059 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No time-sensitive price oracle consumed by the bridge function. Validator-set consensus has liveness requirements at the Cosmos chain level (epoch finality). The staleness-check factor is not applicable to the validator-consensus trust model.
Sources #
- GitHubAxelarGateway.sol sourceAxelarGateway.sol — no oracle staleness check needed; no oracle call presentretrieved 2026-05-17
Methodology #
Determine whether the protocol rejects oracle reads older than a declared maximum age (i.e., checks `updatedAt > block.timestamp - maxStaleness`).
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol axelar factor RD-F-059 score green collected_at 2026-05-16 21:57:49