Max-deviation threshold (bps)
A oracle & external dependencies factor in the v1.7.0 rubric. Measured per protocol on a s cadence.
Methodology how we score#
What this measures
This factor records the specific circuit-breaker threshold configured for oracle price deviation, expressed in basis points (bps). This field is only populated when RD-F-057 confirms a circuit breaker exists; the value is read directly from on-chain configuration or governance parameters.
Why it matters
The presence of a circuit breaker (RD-F-057) is necessary but not sufficient — the threshold calibration determines whether it provides meaningful protection. A 10,000 bps (100%) threshold circuit breaker is nearly useless for assets that can be moved 50x via flash loans. Conversely, an excessively tight threshold (10–20 bps) on a volatile asset may trigger false positives during normal market conditions, causing unnecessary protocol pauses. The threshold must be calibrated to the asset's natural volatility and the minimum manipulation cost given available liquidity, creating a per-asset configuration requirement that curators must verify against oracle pool depth (RD-F-055).
Green / Yellow / Red
Green is scored when the threshold is within the range of 200–2000 bps (2–20%) and is documented as calibrated to the asset's historical volatility profile. Yellow is scored when the threshold exists but is either too wide (over 2000 bps for stable assets) or too narrow (under 100 bps for volatile assets). Red is scored when no threshold is configured (i.e., circuit breaker field is N/A because RD-F-057 is red).
Common gray cases
Gray is applied when the threshold is set dynamically by an off-chain keeper and the current value cannot be read from a public on-chain configuration.
Notable historical examples
No cross-hacked incidents are currently linked in the database for this factor.
Measurement what to look for#
If a circuit breaker exists, read the configured deviation threshold in basis points.