We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
signMessage
Is your feature request related to a problem? Please describe.
See the motivation section in the NEP-413
Describe the solution you'd like
Design and implement support of the signMessage API defined in the NEP-413.
Additional context
Wallets will need to implement the support from their side as well.
If there are any design or security concerns with the NEP-413, consider raising them in near/NEPs#413
P.S. This issue was highlighted through the DevGov Gigs Board
The text was updated successfully, but these errors were encountered:
Hi @frol thanks for raising this issue. This is related to issue #434 and we are internally discussing with @MaximusHaximus how to approach it
Sorry, something went wrong.
Closing in favor of #434.
No branches or pull requests
Is your feature request related to a problem? Please describe.
See the motivation section in the NEP-413
Describe the solution you'd like
Design and implement support of the
signMessage
API defined in the NEP-413.Additional context
Wallets will need to implement the support from their side as well.
If there are any design or security concerns with the NEP-413, consider raising them in near/NEPs#413
P.S. This issue was highlighted through the DevGov Gigs Board
The text was updated successfully, but these errors were encountered: