Add Spending Limit Reset Audit with Tamper-Evident Log

[miss-yusrah]

Labels: contract security feature 200pts

Background:
Spending limits reset periodically. If an admin can silently reset limits early, they could bypass budget controls. Every limit reset must be auditable and tamper-evident.

Problem:
Spending limit resets happen implicitly when Temporary storage expires. There is no log of resets. An early manual reset by an admin is indistinguishable from normal TTL expiry.

What "Done" Looks Like:

• Every spending limit reset (whether TTL-natural or manual) writes an entry to the audit log
• manual_reset_spending_limit(token: Address, period: SpendingPeriod) requires 2-of-N signer approval (mini-proposal)
• SpendingLimitResetRecord: { ledger: u32, token: Address, period: SpendingPeriod, trigger: ResetTrigger, authorized_by: Vec<Address> }
• ResetTrigger::Natural (TTL expiry detected) vs ResetTrigger::Manual(reason: Symbol)
• Reset records stored in Persistent storage (never auto-evict)
• Tests: natural reset logging, manual reset with approval, unauthorized manual reset rejection

Key Files:

• contracts/vault/src/lib.rs
• contracts/vault/src/storage.rs
• contracts/vault/src/types.rs
• contracts/vault/src/test_audit.rs

PR Must Include:

• SpendingLimitResetRecord type
• Manual reset mini-proposal flow
• Audit logging on all reset paths
• 7+ tests

---

[dunnidev]

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

Good day maintainer, i will like to fix this issue

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

[lunaxoxooo]

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

hi maintainer, i want to work on this issue.

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

[drips-wave]

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

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