⏳ Implement Time-Based Expiration and Auto-Refund Mechanism

[Cedarich]

Description
Protect buyers from unresponsive sellers by implementing a time-lock mechanism. If the deadline passes without confirmation or dispute, the buyer can reclaim their funds.

Requirements and Context

• Background: If a seller vanishes, the buyer's funds shouldn't be locked forever.
• Problem: Currently, funds rely on manual action. We need a fail-safe based on the ledger timestamp.
• Success Criteria:
  • Use env.ledger().timestamp() to compare against escrow.deadline.
  • Implement refund_expired(env, escrow_id).
  • Ensure logic handles "Disputed" state (disputes should pause expiration).
• Impact: Automates trustlessness; the contract enforces time limits without human intervention.

Suggested Execution

1. Ensure Escrow struct has a deadline: u64 field.
2. Implement refund_expired:
   • Retrieve escrow.
   • Check current_timestamp > escrow.deadline.
   • Check status is Funded (not Disputed/Completed).
   • Transfer funds back to Buyer.
   • Update status to Refunded.

Test and Commit

• Testing: Mock the ledger timestamp in tests to fast-forward time. Verify refund works after deadline but fails before.
• Commit Message: feat(contract): implement expiration and auto-refund logic

Guidelines

• Handle time carefully (Stellar ledger timestamps are seconds since epoch).
• PR Requirement: Closes #issue

[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

[OlufunbiIK]

@OlufunbiIK has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi maintainers,

Please can I work on this issue?

I promise to deliver

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

[drips-wave]

Congratulations, @OlufunbiIK! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

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