External keeper/relayer not redundant
Multipli's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
xToken vaults depend on ORACLE role address(es) to call onUnderlyingBalanceUpdate() — functionally a keeper/reporter role. If ORACLE role holder goes offline, vault share price is not updated until PPS circuit breaker triggers or admin intervenes. ORACLE role holder identity and redundancy not publicly disclosed — single vs. multiple keeper unknown. rwaUSD: similar dependency on SignedFeedVerifier signers. No keeper-redundancy documentation found.
Sources #
- GitHubMultipliVault.sol — keeper dependency on ORACLE roleMultipliVault.sol — onUnderlyingBalanceUpdate restricted by requiresAuth (ORACLE role); single-role update pattern with no fallbackretrieved 2026-05-17
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →