Skip to content

Add v1/users/address to find user IDs by associated wallet or account addresses#285

Merged
rickyrombo merged 3 commits intomainfrom
mjp-addresses
Aug 1, 2025
Merged

Add v1/users/address to find user IDs by associated wallet or account addresses#285
rickyrombo merged 3 commits intomainfrom
mjp-addresses

Conversation

@rickyrombo
Copy link
Copy Markdown
Contributor

Finds user IDs associated with given addresses of wallets or accounts.

This not only enables the Discord bot to do signature recovery and find the relevant account without needing us to change the authentication of the v1/users/account/:wallet route, but also allows for more general user locating based on associated addresses by any means besides just their account wallet, which opens the door to doing "1-click purchase" if a user buys with a connected wallet on a third party site, etc.

TODO:

  • Add test
  • Swagger

Copy link
Copy Markdown
Contributor

@schottra schottra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minorly grumpy about having multiple endpoints to use for looking up a user by wallet. But, I think this makes sense and is how we would ideally like the other "get user by wallet" endpoints to work.

Comment thread api/server.go Outdated
Comment thread api/v1_users_addresses.go
Comment thread api/v1_users_addresses.go
@rickyrombo rickyrombo changed the title Add v1/users/addresses to find user IDs by associated wallet or account addresses Add v1/users/address to find user IDs by associated wallet or account addresses Aug 1, 2025
@rickyrombo rickyrombo merged commit a56d885 into main Aug 1, 2025
3 checks passed
@rickyrombo rickyrombo deleted the mjp-addresses branch August 1, 2025 16:44
rickyrombo added a commit that referenced this pull request Aug 1, 2025
This endpoint doesn't exist in API and is superceded by #285 anyway

I propose we remove it entirely.

Alternative: mark as deprecated, update loadbalancer to point to dn?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants