feat: implement oracle data staleness and confidence interval validation

[greatest0fallt1me]

Description:

Validate oracle data freshness (staleness) and, where applicable, confidence intervals (e.g., Pyth) before accepting a result for resolution.

Requirements and Context:

• Must be secure, tested, and documented
• Should reject oracle result if data is older than configured max age (e.g., 60 seconds)
• Should for Pyth (or similar) validate confidence interval within threshold (e.g., 5%)
• Should allow admin to configure max staleness and confidence threshold per event or globally
• Should emit events when validation fails
• Must integrate with existing oracle resolution path

Suggested Execution:

1. Fork the repo and create a branch

   git checkout -b feature/oracle-staleness-confidence

2. Implement changes

   • Write contract: validation in oracle resolution path
   • Update oracles module: src/oracles.rs (staleness and confidence checks)
   • Update types and storage; add documentation and NatSpec-style comments

3. Test and commit

   • Run tests; cover stale data rejected, confidence too wide rejected
   • Include test output and security notes

Example Commit Message:

feat: implement oracle data staleness and confidence interval validation

Guidelines:

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 72 hours

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Ekenesamuel8]

@Ekenesamuel8 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I can take this oracle validation task. I’ll add configurable staleness checks (max age) and, for Pyth-style feeds, confidence interval threshold validation before accepting oracle results during resolution. I’ll support global defaults plus per-event overrides, emit events when validations fail, and integrate checks into the existing oracle resolution path. I’ll add tests for stale data rejection and confidence-too-wide rejection and include security/coverage notes (≥95%).

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ekenesamuel8 to this issue.

[drips-wave]

Congratulations, @Ekenesamuel8! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Ekenesamuel8: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊