[SC-ESC-019] Escrow System Optimization and Validation Checkpoint - Step 19

[soomtochukwu]

Implement Dynamic Storage Allocation Recouping (State De-allocation)

• Category: Smart Contract: Escrow & Token Lockup
• Task ID: SC-ESC-019

Description

This issue is dedicated to the technical design, implementation, and rigorous auditing of 'Implement Dynamic Storage Allocation Recouping (State De-allocation)' inside the Lance marketplace ecosystem, specifically focusing on the Smart Contract: Escrow & Token Lockup 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

• Analyze the corresponding storage keys and traits in contracts/escrow/src/lib.rs for Implement Dynamic Storage Allocation Recouping (State De-allocation).
• Implement checked arithmetic calculations using Rust's checked_add and checked_mul to avoid overflow vulnerabilities.
• Ensure that the auth framework (env.require_auth) is strictly integrated for all state-modifying actions.
• Expose public getter functions to query active escrow parameters and balances from persistent storage.

Acceptance Criteria

• The contract builds successfully and compiles to a highly optimized WASM target.
• All related test suites pass successfully with zero gas-limit violations.
• Attempting to invoke state changes without proper authorization yields a strict 401 equivalent error.

[Ejirowebfi]

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

Hi, I'd like to apply for this issue.

I'm a full stack developer (3–5 years) comfortable across the entire stack — from database schema and API design to React/TypeScript frontend and deployment. I regularly work on features that touch both layers, so I'm used to tracing bugs that cross the frontend/backend boundary.

For this specific issue, I plan to: [e.g. audit the API response shape, fix the mismatch on the server side, then update the frontend to handle the corrected structure and add a test for both layers]. I've worked with [technologies mentioned in the issue].

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

[Jenola344]

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

Hi Dxmaker, I will love to work on this

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

[drips-wave]

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

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