Add blacklist idempotency and precedence tests for blacklist_add/blacklist_remove and report_revenue snapshot

[thlpkee20-wq]

Description

blacklist_add and blacklist_remove are documented as idempotent and issuer-only, and the blacklist is snapshotted into report_revenue events. Tests should confirm double-add does not duplicate, double-remove is a no-op, and that the blacklist vector embedded in rev_init/rev_ovrd events reflects the current set. Add this coverage including blacklist-over-whitelist precedence.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: src/lib.rs (blacklist_add, blacklist_remove, is_blacklisted, get_blacklist, report_revenue)
• Confirm a non-issuer caller cannot mutate the blacklist

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/blacklist-idempotency-tests
• Implement changes
  • Add same investor twice, assert get_blacklist length unchanged
  • Remove a non-present investor, assert no panic and no event drift
  • Report revenue and assert event blacklist payload matches current set
• Validate security and correctness assumptions

Test and commit

• Run tests
  • cargo test
• Cover edge cases
  • Empty blacklist snapshot, blacklist after transfer, blacklist+whitelist same address
• Include test output and security notes

Example commit message

test: cover blacklist idempotency and event snapshot fidelity

Guidelines

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

[Zainab5970]

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

please can i work on the issue

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

[drips-wave]

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

🧑‍💻 @Zainab5970: 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 completed by @Zainab5970 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Zainab5970: 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. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.