-
Notifications
You must be signed in to change notification settings - Fork 151
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.
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
Add support for signInMessage method #921
Labels
Emerging Tech
Emerging Tech flying formation at Pagoda
Comments
trechriron
added
Emerging Tech
Emerging Tech flying formation at Pagoda
Near BOS
labels
Sep 13, 2023
14 tasks
Moving this to "In Progress" as I will need to:
|
Moving this into Review as the above improvements have been addressed. |
Moving this into progress to add support for signInMessage in Sender since they implemented the signMessage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This task is about adding the signInMessage method to the API of the wallet selector.
This new method/function(way) will allow dApp users to "sign-in/login" into a dApp without a contractId (without LAK) by signing a message in the wallet based on the NEP413 standard for signing messages.
Once the message is signed and verified wallet selector will set the state as "signed-in".
Kujtim Prenku
2 days ago
After the call on Thursday, these are the steps we’re working on right now:
CleanUp messages on signOut
Kujtim Prenku
August 28, 2023 at 1:24 AM
Hi @daryl Collins, I have a few questions about the implementation of this signInMessage feature:
Kujtim Prenku
August 14, 2023 at 9:50 AM
HI @jacob Nall , this is the ticket for signInMessage in our examples at the moment I am just showing a new button next to the login button, this only opens the modal and if an option is clicked it will trigger the signInMessage of that option:
PR: #883
Should we inform the user what this “Sign In Message” does in a small popup before opening the wallet-selector’s modal?
The text was updated successfully, but these errors were encountered: