Precision-Optimized Binary Storage

[hman38705]

Issue #19:

Developer Goal: Drastically reduce market creation and betting gas costs by minimizing the ledger footprint of the Market and Bet structs.

Technical Context: Ledger storage on Soroban is expensive. Default Rust serialization (XDR) can be verbose. Using bit-packing and Bytes instead of Vec<String> for metadata can save significant costs.

Detailed Requirements:

1. Metadata Compression: Store the market description and options as a single Bytes object containing a compressed JSON or a custom binary format.
2. Bit-Packing:
   • Combined MarketStatus (u8), WinningOutcome (u8), and Tier (u8) into a single u32 "Header" field.
   • Pack boolean flags (is_disputed, is_cancelled, has_oracle) into bit-flags (0x01, 0x02, etc.).
3. Storage Pruning: Implement a "Garbage Collection" function that allows any user to delete Bet data for markets that have been Resolved for more than 180 days, rewarding the caller with a tiny "Clean-up Fee".

Verification Checklist:

• Comparison of gas costs for create_market before and after optimization. Aim for >20% reduction.
• git checkout -b features/issue-19-Precision-Optimized Binary Storage
• Pr Request create your pr against develop branchv

[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

[henrypeters]

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

Hi I'm a full stack developer developer, and I would love to work on this issue

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

[Xoulomon]

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

Hey, Can I work on this Issue.

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

[drips-wave]

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

🧑‍💻 @Xoulomon: 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 @Xoulomon as part of the Stellar Wave Program's 2nd Wave 🥳

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