Oracle role per asset

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

Evidence summary #

No oracle-to-asset mapping exists. stHYPE/HYPE exchange rate derived from internal shares math (balancePerShare()). The rebase 'feed' is the keeper-submitted uint256 l1Balance — a staking balance read, not a price oracle. No primary/secondary/fallback oracle roles to map.

Sources #

Etherscan
OverseerV1 implementation on HyperEVMScanOverseerV1 implementation 0xaC43e7a1467bf6a4db24bf1f121fb59be6c9f831 — rebase(uint256 l1Balance) ABI entry confirms balance parameter, not priceretrieved 2026-05-17
GitHub
stHYPE SDK ABI — stHYPE.jsonValantisLabs/sthype-sdk abis/stHYPE.json — balancePerShare(), balanceToShares(), sharesToBalance() functions; no oracle interfaceretrieved 2026-05-17

Methodology #

For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.

See the full factor methodology and distribution across all protocols →

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