Add Pause/Unpause Mechanism to Vault

[greatest0fallt1me]

Description
Add a pause flag and only allow deposit/deduct when not paused. Only owner (or admin) can pause and unpause. Emit Paused/Unpaused events. Useful for emergency stop.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• When paused, deposit and deduct revert; balance and get_meta still readable

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/vault-pause
• Implement changes
  • Add storage paused: bool; set false in init; add pause() and unpause() (owner-only); in deposit and deduct require !paused
  • Add tests: when paused deposit and deduct panic; unpause restores
• Test and commit
  • Run tests; include test output and security notes
• Example commit message: feat: pause and unpause vault

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours
• Project details: #

[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

[Hallab7]

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

i would like to work on this issue

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

[codeZe-us]

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

Hi, i can get this done, i understand the task

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

[Bosun-Josh121]

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

Hello,

I am an active open-source contributor and I have a strong background in backend and smart contract engineering (specifically Stellar/Soroban) and I would like to tackle this issue.

This issue aligns perfectly with my skillset as I have previously built similar functionality and have reviewed the current codebase, so I am prepared to navigate the architecture without issues.

I can commit to delivering a clean, tested solution within 24 hours. I value clear communication and i'm happy to iterate on any feedback during the review process.

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

[drips-wave]

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

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