Skip to content

[GrantFox][High] Enforce oracle freshness before market settlement #900

Description

@greatest0fallt1me

Summary

Enforce oracle freshness before market settlement

Why this matters

Settlement must not use stale, missing, or contradictory price data.

Scope

Add explicit freshness, quorum, deviation, and fallback checks with auditable rejection reasons.

Acceptance criteria

  • Stale data cannot settle a market.
  • Quorum and deviation boundaries are deterministic.
  • Fallback behavior is explicit and safe.
  • Tests cover outage, recovery, invalid prices, and clock skew.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

  • Typo-only, formatting-only, or documentation-only changes.
  • Unrelated refactors or dependency upgrades.
  • Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions