-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Introduce gaiacli keys export
/ gaiacli keys import
#2020
Comments
Our view has that people need to store their words and that's our portability solution. I disagree that this is |
second zmanian, exporting the seed phrase should be sufficient |
That would be fine if it were possible but it isn't because we don't store the seed phrase. I think we want some export method that can happen after you first create the key, otherwise users who fail to write down their seed phrase - but still have the It's a non-breaking change - so OK on post-launch - I expect we'll get requests for this pretty quickly. |
Sounds like we still don't have |
Correct, we do not have this atm. As I see it, we can:
|
We can export the private key in ASCII format - provided that the user supply the correct mnemonic. |
@alexanderbez storing the seed is in my opinion the most riskiest of all options |
The problem is that the users doesn't know the seed. They were silly and forgot to save it in a safe location. |
I'll spike on this and demo something soon |
So would the seed phrase be accessible in clear text or GPG signed -> requiring password to access it? |
[Brain dump mode ON] A malicious actor sits next to me. By mistake I run [brain dump mode OFF] |
Add Keybase's ExportPrivKey()/ImportPrivKey() API calls to export/import ASCII-armored private keys. Relevant keys subcommands are provided as well. Closes: #2020
and how import key when you saved generated key and didn't save "export" file? |
gaiacli keys unsafe-import-eth-key keyname key |
We definitely need these prelaunch. They can come with extensive warnings.
Ideally we should do this in a standard format; the ASCII-armored one currently in the keybase implementation should be fine for now.
The text was updated successfully, but these errors were encountered: