Repository navigation
Implement milestone-based release schedules in escrow contract #299
Description
Description — what to implement and the why/impact.
The escrow contract (contracts/escrow) currently supports simple lock-and-release mechanics. This task adds support for milestone-based fund releases, allowing partial withdrawals as discrete project milestones are validated and approved.
Context & Requirements — background, constraints, design references, edge cases; grounded in the actual repo (real files, stack, conventions).
- Workspace member:
contracts/escrow - Soroban SDK:
soroban-sdk = "21.7.7" - Partial release amounts must sum up correctly without leaving dust or over-releasing funds.
- Edge cases: Releasing funds for invalid milestone indices and duplicate milestone approvals.
Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".
- Define milestone struct and storage schema in
contracts/escrow/src/storage.rs. - Implement milestone submission and approval functions in
contracts/escrow/src/lib.rs. - Add unit tests verifying partial fund disbursements per milestone.
Implementation Guidance — likely files/modules to touch (use real paths from the repo context) and a suggested approach, without over-prescribing.
- Modify
contracts/escrow/src/lib.rsandcontracts/escrow/src/storage.rs.
Testing & Validation — how the contributor should prove it works (tests to add/run, manual checks, screenshots for UI).
- Run
cargo test --package astroid-escrowto validate escrow behavior.
Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting; follow the repo's existing style and conventions.
Wave complexity: Medium
Activity
Oluwaferanmi18 commentedon Sep 25, 2026
@Oluwaferanmi18 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwaferanmi18 to this issue.
drips-wave commentedon Sep 25, 2026
Congratulations, @Oluwaferanmi18! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Oluwaferanmi18: 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 🌊
feat(escrow): milestone-based release schedules — storage schema, par…
feat(escrow): milestone-based release schedules — storage schema, par…
drips-wave commentedon Oct 7, 2026
This issue has been marked as completed by a Drips Wave moderator for @Oluwaferanmi18 as part of the Stellar Wave Program's 9th Wave 🥳
Moderator's reason: [Auto-assessed] Pull request #362 was merged by maintainer Cjay-Cyber-2 on 2026-10-07, successfully closing issue #299.
😎 @Oluwaferanmi18: 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.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.