Skip to content

Access control list: blocked addresses cannot participate #45

@greatest0fallt1me

Description

@greatest0fallt1me

Description

Optional blocklist for payer/recipient per compliance design; reject create if address blocked.

Requirements and context

  • Highly regulated; default off.
  • Admin role documented.

Suggested execution

  • Fork the repository and create a branch (example below).
  • Implement the changes in the StreamPay-Contracts Soroban crate (streampay-contracts).
  • Keep the contract secure, tested, and documented; prefer small, reviewable diffs.
git checkout -b feature/compliance-blocklist

Implementation targets

  • Storage for set of addresses (bounded strategy).
  • Tests add/remove/list.

Tests and validation

  • Add or extend contract tests for this scope.

  • Cover edge cases; paste summarized test output and security notes in the PR.

  • Run cargo test in StreamPay-Contracts.

  • Cover edge cases; capture test output and short security notes in the PR description.

Guidelines

  • Target minimum 95% test coverage for touched contract code (or justify gaps explicitly).
  • Clear documentation (rustdoc / project docs as specified).
  • Timeframe: 96 hours from assignment.

Example commit message

feat(contracts): optional address blocklist for streams

Metadata

Metadata

Assignees

No one assigned
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions