[SC-031] Restrict Mutating Methods When Paused

[thlpkee20-wq]

Description

Develop and deliver restrict mutating methods when paused with production-grade quality, including implementation, tests, and documentation aligned with ChronoPay architecture.

Requirements and context

• Must be secure, tested, and documented.
• Should be efficient and easy to review.
• Scope is limited to ChronoPay-Contracts/contracts/chronopay/src.
• Include clear acceptance criteria and failure-mode handling.

Suggested execution

1. Fork the repo and create a branch.
2. git checkout -b feature/sc-031
3. Implement changes in the scoped modules.
4. Add/expand automated tests.
5. Add docs and inline comments for non-obvious logic.
6. Validate security assumptions and edge cases.

Test and commit

• Run full test suite and relevant targeted tests.
• Cover edge cases, invalid inputs, and authorization paths.
• Include test output and short security notes in PR/issue updates.

Example commit message

feat(contract): restrict mutating methods when paused

Guidelines

• Minimum 95% test coverage for touched modules.
• Clear documentation for behavior, assumptions, and constraints.
• Target timeframe: 96 hours.

[RennyThompson]

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

hello there i would love to take on this issue considering my experience and my engagement to the previous wave.

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

[drips-wave]

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

🧑‍💻 @RennyThompson: 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 @RennyThompson as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: The issue was resolved and merged in PR: #110

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