Oracle price deviation >X% from secondary
Kinetiq's assessment for RD-F-099 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 phase-2 signal. Applicable in principle: yes. Kinetiq uses a proprietary push-oracle (Operator→OracleManager→StakingAccountant) for the kHYPE/HYPE exchange rate — not a Chainlink/Pyth primary feed. No independent secondary feed exists for this rate. The T-09 standard detection rule (primary vs secondary feed comparison) cannot be applied as-is. A custom rule comparing the daily pushed rate against an independently computed NAV would be needed. Pipeline unimplemented. Data cache oracle_feeds: [] confirms no standard feed mapping.
Sources #
- EtherscanKinetiq OracleManager — HyperEVMScanOracleManager proxy 0x192826e4 — internal push-oracle; no external Chainlink/Pyth feed to compare againstretrieved 2026-05-17
Methodology #
Detect whether the primary oracle's reported price deviates >X% from the best available secondary source (another feed or venue).
See the full factor methodology and distribution across all protocols →