Skip to content

Add unit tests for the blacklist view returning the correct status for blacklisted and non-blacklisted wallets #725

Closed

Description

@Chucks1093

Summary

A is_blacklisted view should return true for a wallet on the blacklist and false for one that is not. Unit tests should confirm both cases and that removing a wallet from the blacklist flips the response.

Scope

  • Test is_blacklisted returns false for a wallet not on the list
  • Test is_blacklisted returns true after the wallet is added to the blacklist
  • Test is_blacklisted returns false after the wallet is removed from the blacklist

Acceptance Criteria

  • Returns false for non-blacklisted wallet
  • Returns true after wallet is blacklisted
  • Returns false after wallet is removed from blacklist

ETA: 12 hours


Coordinate on Telegram

Activity

  1. Akinloluwa20 commented on Aug 24, 2026

    @Akinloluwa20

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

    I would like to work on this issue

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

  2. Unclebaffa commented on Aug 24, 2026

    @Unclebaffa
    Contributor

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

    Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
    I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
    If it's available, please assign it to me. Thank you!

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

  3. Izzyabbey2020 commented on Aug 24, 2026

    @Izzyabbey2020

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

    Hi there, I carefully reviewed the issue details and I’m confident i can deliver a clean and efficient solution.

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

  4. Cmitchelle7 commented on Aug 24, 2026

    @Cmitchelle7
    Contributor

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

    Hi Maintainer, reviewed the issue in detail. Full stack background with solid experience relevant to this task. No blockers on my end — I'm ready to submit a PR shortly. Please assign.

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

  5. sladeoj commented on Aug 24, 2026

    @sladeoj

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

    hii maintainer can i work on this issue please

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

  6. josephinejose-alt commented on Aug 24, 2026

    @josephinejose-alt

    @josephinejose-alt has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    studied the task at hand and i can say i have a clear understanding
    pls assign me so i can begin implementation

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

  7. drips-wave commented on Aug 24, 2026

    @drips-wave

    Congratulations, @Cmitchelle7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

  8. added a commit that references this issue on Aug 25, 2026
  9. grantfox-oss commented on Aug 25, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

    @Cmitchelle7's PR #735 was approved and merged by @Chucks1093.

    🏆 @Cmitchelle7: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (987 total points). Track your full progress on GrantFox.

    👏 Great work, @Cmitchelle7! Keep contributing to accesslayerorg.

  10. drips-wave commented on Aug 25, 2026

    @drips-wave

    This issue has been completed by @Cmitchelle7 as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @Cmitchelle7: You earned 150 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions