Oracle staleness check present

SUNSwap (sun.io)'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 oracle staleness check exists or is needed. No external oracle data enters any SUNSwap contract, so there is no `updatedAt` timestamp to validate. Confirmed by zero oracle imports in V2/V4 core contracts.

Sources #

GitHub
V4 PoolManager.sol — no staleness checksun-protocol/sunswap-v4-core: contracts/PoolManager.sol — zero oracle imports, no updatedAt checkretrieved 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 sunswap factor RD-F-059 score not_applicable collected_at 2026-05-17 14:37:31