Chainlink aggregator min/max bound misconfig
Spiko's assessment for RD-F-060 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Spiko's Oracle contract is a custom implementation of AggregatorV3Interface, not a standard Chainlink aggregator with minAnswer/maxAnswer circuit breakers. The minAnswer/maxAnswer misconfig factor applies to standard Chainlink feed contracts, not to custom implementors of the interface.
Sources #
- EtherscanSpiko Oracle implementation — EtherscanOracle impl 0xcbeb19549054cc0a6257a77736fc78c367216ce7 — custom Oracle.sol implementing AggregatorV3Interface, no Chainlink AggregatorV2V3Interface minAnswer/maxAnswerretrieved 2026-05-16
Methodology #
Determine whether the Chainlink aggregator's `minAnswer` and `maxAnswer` circuit-breaker bounds are misconfigured (too wide or too narrow) for the asset class.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol spiko factor RD-F-060 score not_applicable collected_at 2026-05-15 22:52:13