we should return wallet addresses in the function too so that we don't accidentally add claimed wallet addresses back to the reserved usernames table
Details
call add_reserved_usernames RPC with a registered wallet address, address filtered out and not added to reserved usernames table
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Accepting, but I noticed one more thing that needs to be considered.
Scan operation doesn't always return all items. It has response limit of 1MB. If it's exceeded, the response contains LastEvaluatedKey property, from which we should start a subsequent scan.
On the other hand, this table is relatively small (1k items, ~60kB) so it's far from the limit. And it's not expected to grow, so we could ignore the issue as well
AWS Docs: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Scan.html
yeah as you said there are about 1k items and not many more will be added so we should expect scan to return all items