Oracle staleness check present
Hyperlane's assessment for RD-F-059 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
StorageGasOracle has no staleness check — exchange rate data is set manually by owner with no timestamp guard. For Chainlink feeds in ERC4626 Warp Routes, staleness check implementation not confirmed from primary source in this session. The ERC4626 collateral contract uses vault.convertToAssets() without a confirmed Chainlink latestRoundData staleness guard.
Sources #
- GitHubStorageGasOracle.sol — no staleness checkStorageGasOracle.sol — no updatedAt staleness guard on gas price dataretrieved 2026-05-17
- HypERC4626Collateral.sol — staleness check not confirmedHypERC4626Collateral.sol — uses vault.convertToAssets(PRECISION) without visible Chainlink latestRoundData staleness guardretrieved 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 hyperlane factor RD-F-059 score yellow collected_at 2026-05-16 23:03:56