Updates "Authenticate NEAR Users", including recommendation for near-sign-verify #2601
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
@elliotBraem this has been stalled for long enough, let me know if you ever want to get back to it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft PR, pending near-sign-verify support for near-wallet-selector.
I want to update the core backend authentication concepts, and modernize the language around NEP-413 -- then provide near-sign-verify as an optional package, with tabbed examples for keypair, near-wallet-selector, and fastnear-js signers. Might even include a reference to Slime's example of validating a signature in Rust: https://gist.github.com/Sliman4/f86f3e5ba04f274b92f22a3357896d02
This PR is far from complete, but any feedback or wishlist is welcome!