Support Multi-Result Oracle Keys

[hman38705]

issues : 9

Great issue: Support Multi-Result Oracle Keys

Description
get_oracle_result uses a hardcoded sub-index 0 for storing results: OracleData::Result(market_id, 0). This restricts the system to only one oracle result per market forever, preventing multi-oracle aggregation or historical retrieval.

Requirements and context

• Incorporate an oracle_id or version into the OracleData key structure.
• Allow querying different outcomes by their respective oracle sources.

Suggested execution

• Fork the repo and create a branch: git checkout -b fix/issue-9-oracle-indexing
• Refactor oracle storage mapping.

Implementation changes

• Modify oracles.rs (around line 89) to replace the hardcoded index with a parameter.

Test and commit

• Verify that multiple oracles can successfully post data to the same market without collisions.

Example commit message
fix: implement flexible oracle result indexing per market

Guidelines

• Extensibility for future tiered oracle systems.
• Timeframe: 48 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

[maztah1]

@maztah1 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I can solve this issue

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @maztah1 as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @maztah1: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.