Chainlink aggregator min/max bound misconfig
Polymarket's assessment for RD-F-060 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Chainlink feeds in data cache (BTC/USD, ETH/USD, etc.) are not consumed by Polymarket's own contracts for collateral pricing or liquidation. No IChainlinkAggregator import in CTF Exchange V2 or UMA CTF Adapter. Chainlink Data Streams (September 2025) uses verifiable off-chain push reports, not the legacy AggregatorV3 min/max bounds pattern. Classic minAnswer/maxAnswer misconfig not applicable to this integration architecture.
Sources #
- EtherscanCTF Exchange V2 — Verified SourceCTF Exchange V2 source — no IChainlinkAggregator importretrieved 2026-04-29
- Polymarket just made Bitcoin bets settle instantly with Chainlink upgradeChainlink Data Streams architecture — off-chain push reportsretrieved 2026-04-29
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 →