Fallback behavior on oracle failure

stHYPE (Valantis Labs)'s assessment for RD-F-051 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

No oracle failure mode in the traditional sense. If REBASER_ROLE keeper stops submitting rebases, syncSupply is not called; no revert or auto-pause is triggered. No declared fallback oracle path. Docs state 'no guaranteed insolvency backstop.' If HyperCore L1 system fails, no alternative data source exists. Yellow: no fallback on keeper failure; fund custody unaffected but LST ceases to accrue rewards.

Sources #

GitHub
OverseerV1 ABIoverseerV1.json ABI — rebase(uint256 l1Balance) has no try/catch or fallback oracle call in function signatureretrieved 2026-05-17
Docs
stHYPE Transparency and Riskstransparency-and-risks: 'no guaranteed insolvency backstop for user losses'retrieved 2026-05-17

Methodology #

Identify the declared fallback behavior (pause, secondary source, last-known-price, revert) when the primary oracle reverts or reports a stale value.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol staked-hype factor RD-F-051 score yellow collected_at 2026-05-17 13:02:38