Address -> username and username -> user rework #975
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reworking the way the dashboard is getting the address to username and the username to user mappings.
Address -> username maps many addresses to a single username. For example, I have 3 wallets mapped to a single bot username.
username -> user maps many usernames to a single user. For example, my bot account and click account gets mapped to a single user for the leaderboard.
These mappings are written to the database and can be live updated with the
update_username.py
script inlib/chainsync/bin
. This script also gets ran during docker initialization (corresponding infra change needed).