Maximum uses per address not respected
Open
Nobody has claimed this yet.
area: wallet
type: bug
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
We have the speech wallet running with 1000/1000 and it has 34K addresses.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report only describes a speech wallet configured with 1000/1000 and 34K addresses; it names no files, tests, or entry points. First reproduce or inspect how the maximum uses per address is configured and applied, then identify why the observed address count exceeds that limit. Done means the configured maximum is respected and a regression test covers the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, python
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100