Test multiple vaults (ID uniqueness and isolation)

[1nonlypiece]

Description
Add a test that creates multiple vaults and verifies vault_ids are unique and that operations on one vault do not affect another (get_vault_state, release, redirect, cancel).

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested execution

• Fork the repo and create a branch
• git checkout -b test/multiple-vaults-isolation
• Implement changes
  • Create several vaults, assert distinct ids and correct state per id
• Test and commit
  • Run tests
  • Include test output and security notes
• Example commit message: test: multiple vaults ID uniqueness and isolation

Guidelines

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

[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

[chukwudiikeh]

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

I’m applying to implement the Vault Isolation and Uniqueness test suite. I have extensive experience with Soroban’s Map and Persistent storage patterns, and I specialize in writing "collision tests" that verify data integrity across multiple contract instances.

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

[Mmesolove]

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

Hi, maintainer I have read through this and I can solve it please assign to me.

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

[drips-wave]

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

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