Oracle staleness check present
Babylon Protocol's assessment for RD-F-059 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No Chainlink latestRoundData() or Pyth staleness check pattern in any Genesis module. x/btclightclient uses Bitcoin block height (PoW) for freshness, not an EVM-style updatedAt staleness check.
Sources #
- GitHubBabylon x/btclightclient modulex/btclightclient — validates Bitcoin headers by PoW; no EVM staleness checkretrieved 2026-05-04
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 babylon-protocol factor RD-F-059 score not_applicable collected_at 2026-05-04 19:43:27