Oracle staleness check present
Sanctum'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 #
Structural characteristic distinct from EVM oracle staleness. LST exchange rates update at each Solana epoch boundary (~2–3 days). Within an epoch the rate is static. There is no staleness window in the EVM 'updatedAt > now - X' sense; instead the rate is epoch-anchored and read live from on-chain state. Infinity V2 introduced continuous yield distribution per slot (reducing in-epoch staleness for yield accrual), but the underlying stake pool epoch mechanics remain. Yellow because the ~2–3 day epoch window creates a period where accumulated epoch yield is not yet reflected in the redemption rate — materially different from EVM heartbeat-based staleness but structurally present.
Sources #
- URLSanctum Launches Infinity V2Infinity V2 launch: 'first Solana LST to distribute yield continuously every Solana slot' — V2 partially mitigates epoch staleness for yield distribution but underlying stake pool epoch mechanics remainretrieved 2026-05-04
- 00-profile.md §7Profile §7: epoch-cadence rate updates are a structural characteristic of Solana LST stake pools; ~2-3 day epoch lengthretrieved 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 →