[SC-REG-024] Job Registry and Proposal Scaling Validation - Step 24

[soomtochukwu]

Optimise Bids Collection Array Bounds in Registry Storage

• Category: Smart Contract: Job Registry & Bidding
• Task ID: SC-REG-024

Description

This issue is dedicated to the technical design, implementation, and rigorous auditing of 'Optimise Bids Collection Array Bounds in Registry Storage' inside the Lance marketplace ecosystem, specifically focusing on the Smart Contract: Job Registry & Bidding component. The focus of this task is on benchmarking resource utilization, streamlining deserialization cycles, and packing storage layouts. You must profile gas usage or computational overhead meticulously to minimize the persistent ledger footprint and ensure highly cost-effective execution. Ensure that your implementation strictly adheres to the project's architectural guidelines, features self-documenting code with comprehensive inline annotations, and provides solid verification proofs. Any modifications to state variables must undergo strict validation before commits.

Requirements

• Scaffold and write the contract logic in contracts/job_registry/src/lib.rs for Optimise Bids Collection Array Bounds in Registry Storage.
• Compress heavy text strings into compact IPFS Content Identifiers (CIDs) before storing on-chain.
• Design clean mappings from Job IDs to dynamic bid structures utilizing map-like storage arrays.
• Implement strict ownership validation so that only the job creator can accept proposals.

Acceptance Criteria

• Contract successfully compiles and fits within the standard Soroban WASM size limits.
• Registry state transitions cleanly to 'Assigned' once a bid is successfully accepted.
• Out-of-bounds inputs or late bid submissions are gracefully blocked and return specific error codes.

[Benedict315]

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

Hello please i would like to work on this issue

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

[drips-wave]

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

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