Support multiple vaults per contract instance via persistent storage map in accountability_vault

[1nonlypiece]

Support multiple vaults per contract instance via persistent storage map in accountability_vault

Description

contracts/accountability_vault/src/lib.rs stores a single Vault under DataKey::Vault in instance storage, so one deployed contract supports exactly one vault. Refactor to key vaults by a vault_id in persistent storage so a single deployment can host many vaults, matching the backend model where each PersistedVault has an id (src/types/vaults.ts). Update all functions to take a vault_id argument.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Change DataKey::Vault to DataKey::Vault(BytesN/Symbol id) in contracts/accountability_vault/src/lib.rs
• Thread a vault_id through create_vault/stake/check_in/slash_on_miss/claim/withdraw
• Use persistent (not instance) storage with TTL bumps
• Add multi-vault tests in contracts/accountability_vault/src/test.rs

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/multi-vault-storage
• Implement changes
  • Modify contracts/accountability_vault/src/lib.rs
  • Add tests in contracts/accountability_vault/src/test.rs
  • Document the keying scheme in contracts/README.md
  • Add storage TTL handling
• Test and commit
  • Run tests, cover edge cases
  • Include test output and notes

Example commit message

feat: support multiple vaults per contract via id keying

Guidelines

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

[Abioladory123]

@Abioladory123 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Interested in taking this on. I’ve worked across smart contracts, APIs, and frontend integrations, and I can start immediately.

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

[drips-wave]

Congratulations, @Abioladory123! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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