Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate lockstacks auth to use getAddresses #196

Open
kyranjamie opened this issue Nov 11, 2024 · 2 comments
Open

Migrate lockstacks auth to use getAddresses #196

kyranjamie opened this issue Nov 11, 2024 · 2 comments
Labels
enhancement-p1 Critical functionality needed by many users, with no clear alternatives

Comments

@kyranjamie
Copy link
Collaborator

In this issue, we'd like to migrate Lockstacks to use our LeatherProvider.request('getAddresses') API.

The motivation for this change is that it offers a more polished user experience, and pushes forward our adoption of the newer APIs.
@314159265359879 314159265359879 added the enhancement-p1 Critical functionality needed by many users, with no clear alternatives label Nov 12, 2024
@314159265359879
Copy link

A user just reported they are switching to Xverse because they ran into the race condition issue with the StacksProvider connect option.

I'd say this is high priority.

Image
https://leather.gitbook.io/

@kyranjamie
Copy link
Collaborator Author

This isn't isn't directly related to migrating to getAddresses. I think we might need to upgrade stacks connect (until the point at which we migrate)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement-p1 Critical functionality needed by many users, with no clear alternatives
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kyranjamie @314159265359879