Custody Return Flow

[amina69]

🎯 Goal

Implement complete custody return lifecycle.

This includes escrow resolution and trust updates.

---

📋 Description

When custody ends (RETURNED):

1. Validate custody is ACTIVE
2. Change status → RETURNED
3. Release escrow (if exists)
4. Emit EventLog:
   • CUSTODY_RETURNED
5. Recalculate trust score
6. Update pet derived availability

If violation:

• Change status → VIOLATION
• Trigger escrow refund logic
• Emit violation event
• Penalize trust score

---

🛠 Tasks

• Implement returnCustody(custodyId)
• Implement violationCustody(custodyId)
• Integrate escrow service
• Emit proper EventLogs
• Trigger trust recalculation service

---

🔄 Flow Example

User returns pet
→ custody.status = RETURNED
→ escrow RELEASED
→ trustScore updated
→ Pet becomes available again

---

✅ Acceptance Criteria

• Successful custody releases escrow
• Violation refunds escrow
• Trust score updated
• EventLog entries created
• Pet availability updated

[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

[Emmzyemms]

@Emmzyemms has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello Maintainers,
I’m a full-stack and smart contract developer with experience building responsive frontend interfaces, scalable backend systems, and secure blockchain applications. I’m interested in contributing to this issue and believe I can deliver a clean, well-tested solution that aligns with the project’s standards.
I’m eager to learn, improve, and collaborate with the community while contributing meaningful value. I would appreciate the opportunity to work on this task.

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

[Christopherdominic]

@Christopherdominic has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi 👋

I’d like to work on this issue.

I’ve reviewed the description and acceptance criteria, and I’m confident I can implement the required changes following the project’s guidelines and coding standards. I’ll ensure proper testing and documentation where applicable.

Please assign this issue to me — I’ll get started right away. 🚀

Thank you!

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

[drips-wave]

Congratulations, @Christopherdominic! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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

[kingjosmel]

@kingjosmel has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I am a Smart Contract Developer, and I will implement the returnCustody and violationCustody lifecycle methods, ensuring atomic state transitions between escrow release, trust score penalties, and pet availability updates.

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

[drips-wave]

Congratulations, @kingjosmel! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @kingjosmel: 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 marked as completed by a Drips Wave moderator for @kingjosmel as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] PR #97 in amina69/PetAd-backend implements the core logic for custody returns and violations, including escrow management and trust score updates. Although the PR is still open, it has been available for review for over six days with no objections, and it directly addresses the tasks outlined in the issue.

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