Contract: Access Control & Authorization

[ogazboiz]

Ensure only authorized parties can cancel or withdraw.

Context:
Prevent griefing or theft. Only the recipient should withdraw. Only sender (or maybe recipient) can cancel.

Independence:
Add checks to existing functions.

Acceptance Criteria:

• Use recipient.require_auth() in withdrawal
• Use sender.require_auth() in cancel
• Test unauthorized access failures

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 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

[Obiajulu-gif]

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

GM maintainer, I’d like to take this because it’s a direct security hardening: I’ll update the contract’s access checks so only the recipient can withdraw (recipient.require_auth() inside the withdraw flow) and only the sender can cancel (sender.require_auth() inside cancel), ensuring there’s no griefing or unauthorized fund movement. I’ll add unit tests that prove unauthorized callers fail deterministically for both paths (non-recipient withdraw attempts and non-sender cancel attempts), while authorized calls continue to succeed as expected.

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Obiajulu-gif as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @Obiajulu-gif: You earned 150 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.