You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The signedIn state logic will be inside the wallet selector, wallet will not be aware of this.
When calling signAndSendTransaction(s) if there's no contract throw "Not signedIn with a contractId."
Save signedMessage in localStorage to persist the accountId and publicKey that was used to sign the message
Create a new function in the selector API to check the sign-in type
async signInType() {
// Returns "key" if we're signed in with signIn
// Returns "message" if we're signedIn with signInMessage
return "key";
}
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:
Is the SignedMessage needed by the dApp developer after the user signs-in via signInMessage?
What happens when we try to call signAndSendTransaction(s) after we sign-in with signInMessage?
Will the wallets implement this method on their side? (Otherwise, the wallet is not aware we're signedin/connected)
We're persisting the "message", should it be removed if the user decides to signIn with a contractId?
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:
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: