-
Notifications
You must be signed in to change notification settings - Fork 32
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
HD wallet from CLI - do we force HD generation on start? #99
Comments
I think we should move to HD wallets only when we are sure that they are safe to use. While users can still backup their wallet.data, the only official recommended way to backup a wallet should be For sure, we need to warn Stex in advance about this change. |
They are safe to use, as the mechanism is identical to that used across 100+ other coins. Wallet or seed, same same. Both are supported backup paths |
Depends on #171 |
Moved to 1.6.0, as it is not required for VM release, no fork required, and we should make sure exchanges are informed/aware. |
This has been resolved to be opt in |
I wonder about exchange updating wallet. Does the startup of CLI on update prompting to create HD key pose a problem to update path for existing wallets?
If I am network admin for an exchange tasked with updating wallet, should I be privy to the HD key backup key/phrase?
Should we allow an option to continue without an HD wallet as default behavior from CLI, and only prompt to create if they try to add a new account from CLI?
The text was updated successfully, but these errors were encountered: