Implement Oracle Price Feed Update Path in Contract

[RUKAYAT-CODER]

Overview

oracle.rs defines types and storage functions but there is no entrypoint to push or update price data. est_oracle.rs is 784 bytes with a single placeholder test.

Background

The oracle is needed to validate reward amounts against live token prices and to prevent quest creators from setting rewards below a minimum USD value.

Specifications

Features:

• set_price(env, caller, token, price_data) entrypoint gated behind OracleAdmin role
• Price staleness check: reject prices older than configurable TTL
• Circuit-breaker: halt new quest registrations when price feed is stale

Tasks:

• Implement set_price in oracle.rsn- Add staleness check in �alidation.rsn- Expand est_oracle.rs with staleness and circuit-breaker tests

Impacted Files:

• contracts/earn-quest/src/oracle.rsn- contracts/earn-quest/src/validation.rsn- contracts/earn-quest/tests/test_oracle.rs`n

Acceptance Criteria:

• Price update accepted from OracleAdmin
• Stale price (>1h) causes quest registration to fail
• All new oracle tests pass

[Gabugo-tech]

@Gabugo-tech has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainers,

I'd like to work on this issue. I have experience with Node.js performance optimization and production monitoring, and I can implement the required resource limits and profiling while ensuring minimal overhead.

I'll add the necessary tests, update documentation where needed, and verify that all existing functionality remains unaffected.

Thanks for your consideration.

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

[believetimothy]

@believetimothy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, I can fix this issue.

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

[drips-wave]

Congratulations, @believetimothy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @believetimothy: 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 awarded 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 🌊