[SC-REG-034] Job Registry and Proposal Scaling Validation - Step 34

[soomtochukwu]

Implement Dynamic Service Fee Adjustments for Job Postings

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

Description

This issue is dedicated to the technical design, implementation, and rigorous auditing of 'Implement Dynamic Service Fee Adjustments for Job Postings' inside the Lance marketplace ecosystem, specifically focusing on the Smart Contract: Job Registry & Bidding component. As a Soroban smart contract task, the contributor must design robust instance or persistent storage allocations, ensure safe checked math operations, and write high-coverage unit tests within the Rust cargo test harness. The compiled WASM footprint must fit comfortably within standard block boundaries. 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 Implement Dynamic Service Fee Adjustments for Job Postings.
• 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.

[extolkom]

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

Please assign me

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

[chiscookeke11]

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

Hello Chief, Please I would love to work on this issue

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

[drips-wave]

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

🧑‍💻 @chiscookeke11: 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 @chiscookeke11 as part of the Stellar Wave Program's 5th Wave 🥳

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