Max-deviation threshold (bps)
StakeWise v3's assessment for RD-F-058 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Partial data: KeeperRewards enforces _maxAvgRewardPerSecond (upper bound, ~6.34B per Etherscan constructor description) preventing extreme upward reward-rate values. This is a one-sided cap, not a bidirectional bps-threshold circuit breaker. No circuit breaker in the traditional deviation-from-reference sense is configured (per F057 finding). Cannot confirm the exact bps equivalent of _maxAvgRewardPerSecond without direct RPC call; data insufficient for a green/yellow/red grade on this factor.
Sources #
- EtherscanKeeper ReadContract — EtherscanKeeper ReadContract description mentions maxAvgRewardPerSecond ~6.34B in constructor; exact bps equivalent requires curator RPC callretrieved 2026-05-16
Methodology #
If a circuit breaker exists, read the configured deviation threshold in basis points.
See the full factor methodology and distribution across all protocols →