we should add eth addresses to the reserved usernames table as well so we can make sure we don't mint new user IDs for these users
Details
Details
verified eth address exists in my localstack ddb reserved usernames table
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
What happens if the API request fails (eg endpoint is unreachable)? We may end up in a state where not all eth addresses make it to the reserved usernames table.
Should we also have some sort of cron script that takes all eth addresses from keyserver DB and hits the addReservedUsernames endpoint to "fix things up" so things are eventually in a correct state?