This repository was archived by the owner on Oct 4, 2024. It is now read-only.
Fixing generate-key with --seedPhrase #1003
Open
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
|
@judith-Near can you please fix tests, since they are broken on master after your last merge. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently when you call
near --generate-key --seedPhrase a b c ..
It will create 2 implicit keys (one with the seedPhrase and the other one with random value) - which is a little bit confusing.
Moreover, I think that something's wrong with seed-phrase.js code - as it should probably store the key in a seedPhraseKeystore (but I'm not very familiar with this code).