Skip to content
This repository has been archived by the owner on Jul 15, 2018. It is now read-only.

keys: Recover from seed without persisting to disk #57

Closed
ebuchman opened this issue Dec 30, 2017 · 4 comments
Closed

keys: Recover from seed without persisting to disk #57

ebuchman opened this issue Dec 30, 2017 · 4 comments
Assignees
@liamsi

Comments

@ebuchman
Copy link
Contributor

We should be able to enter a seed and use a privkey without that privkey ever being saved to disk
@ebuchman
Copy link
Contributor Author

Oh - maybe that's just using memDB!

@ebuchman ebuchman changed the title keys: Recover should have a non-persistent option keys: Recover from seed without persisting to disk May 8, 2018
@ebuchman ebuchman mentioned this issue May 8, 2018
Closed
@ebuchman
Copy link
Contributor Author

ebuchman commented May 8, 2018 •
edited
Loading

The recover flow should enable us to specify an HD path as well. See #90

@liamsi liamsi mentioned this issue Jun 12, 2018
Merged
@liamsi
Copy link
Contributor

liamsi commented Jun 12, 2018 •
edited
Loading

We should be able to enter a seed and use a privkey without that privkey ever being saved to disk

#118 tackles this the following way: if given an empty password, the (private) key is not persisted.

The recover flow should enable us to specify an HD path as well. See #90

possible in #118 (BIP 44 is fully supported by keybase API, arbitrary BIP 32 paths are also supported via the hd package, i.e. without the persistence support etc)

@liamsi
Copy link
Contributor

liamsi commented Jul 3, 2018

Possible via not providing a password to encrypt on disk (code moved over to cosmos-sdk).

@liamsi liamsi closed this as completed Jul 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@liamsi liamsi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebuchman @liamsi