🛑 Implement Emergency Circuit Breaker (Pause/Unpause)

[Cedarich]

Description
Add security functionality allowing the Admin to pause contract operations in case of a discovered vulnerability or network issue.

Requirements and Context

• Background: Smart contracts are immutable, but operational control is needed for emergencies.
• Problem: If a bug is found, we cannot stop users from depositing funds.
• Success Criteria:
  • Implement set_paused(env, bool) (Admin only).
  • Add a check ensure_not_paused(env) to all state-changing functions (create, release).
• Impact: Critical risk mitigation feature.

Suggested Execution

1. Add State enum to storage (Active, Paused).
2. Implement set_pause function requiring Admin auth.
3. Add a helper fn check_active(env) that panics if state is Paused.
4. Call check_active at the start of create_escrow and confirm_delivery.

Test and Commit

• Testing: Pause the contract and verify create_escrow fails. Unpause and verify it succeeds.
• Commit Message: feat(contract): implement emergency circuit breaker

Guidelines

• Read-only functions (getters) should likely remain accessible even when paused.
• PR Requirement: Closes #issue

[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

[Yusufolosun]

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

Hi Maintainer, Good day
I’d like to implement the emergency pause mechanism to add a proper circuit breaker to the contract. Please assign issue to me

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

[gelluisaac]

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

I’m interested in tackling this! I have a strong background in smart contract development and full-stack systems, so I'm well-equipped to handle the requirements here. Could you please assign this to me?

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

[drips-wave]

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

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

Moderator's reason: The issue was resolved by the contributor and merged by the maintainer in PR:
#45

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

🧑‍💻 Repo maintainers: How'd the contributor do? If you like, you can reward them with additional points by making a compliment within seven days after the Wave Program's current wave ends.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.