Automated Gas Benchmarking & Instruction Optimization

[hman38705]

Descriptions:

Issue #7:

Developer Goal: Ensure the contract stays within Soroban's strict CPU and memory limits, especially during the iteration over many outcomes or bettors.

Detailed Tasks:

1. Iteration Audit: Review resolve_market and any potential loop that iterates over a Vec.
2. Asymptotic Logic: If a market has thousands of winners, switch from "Push" payouts (one transaction) to "Pull" payouts (each user claims their own - see Issue Advanced Payout & Reward Distribution system #1).
3. Storage Costs: Optimize the Market struct using Option<u32> instead of large default integers where possible to save on ledger footprint costs.

Verification Checklist:

• Script with soroban contract invoke that measures instructions for a 100-outcome market.
• git checkout -b features/issue-7-Automated Gas Benchmarking & Instruction Optimization
• Pr Request create your pr against develop branch

---

[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

[Yusufolosun]

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

Gooday Maintainer,
I’ve carefully reviewed the issue description and would like to take this on. I understand the requirements and will implement the solution in alignment with the existing project structure and standards.

Would proceed and do a great work once assigned

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

[Markadrian6399]

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

i would like to apply

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Markadrian6399 as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @Markadrian6399: 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.