External keeper/relayer not redundant
mETH Protocol'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 #
OracleQuorumManager uses dual-threshold quorum (absoluteThreshold + relativeThresholdBasisPoints) — not single-reporter dependency. Multiple SERVICE_ORACLE_REPORTER role members configured. However: (a) initial constructor parameters showed absoluteThreshold=1, relativeThresholdBasisPoints=0 (current production values unverified), (b) if all reporters go offline simultaneously, rate freezes indefinitely. LiquidityBuffer rebalancing is admin-triggered (not a keeper). No third-party keeper for core operations.
Sources #
- GitHubOracleQuorumManager.sol — reporter quorum setupmantle-lsp/contracts src/OracleQuorumManager.sol — initialize() with absoluteThreshold=1, relativeThresholdBasisPoints=0; SERVICE_ORACLE_REPORTER role setupretrieved 2026-05-16
- OracleQuorumManager — Etherscan activityOracleQuorumManager proxy 0x92e56d2146D54d5AEcB25CA36c89D027a6ea0D90 — active receiveRecord transactions confirm committee is operationalretrieved 2026-05-16
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 →