-
Notifications
You must be signed in to change notification settings - Fork 31
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
is there any way to recover wallet.data from mnemonic?? #279
Comments
When you create new wallet, ignore its new mnemonic. Confirm new mnemonic only once to launch the wallet gui. |
We have an open issue for adding this feature to the initial screen of wallet creation #261 |
(1)I first create a wallet, the mnemonic is then, i remove the wallet.data。and create a new wallet and then i select in top menu go to Wallet ->"Reset HD wallet mnemonic phrase" and use my OLD mnemonic to reset, but the private key i get is how i can restore my OLD private key???? |
@amazingMan2017 first of all don't ever share your private keys and mnemonic phrases in the internet. Even if those public addresses don't have money now, you can forget or send by mistake some coins to those accounts later. You can restore from mnemonic only accounts that were derived from it after HD wallets were introduced. Legacy accounts which were created before you generated and saved your old mnemonic cannot be restored from it because they have nothing to do with the new seed and their public/private key pairs existed long before it. You need a |
It may be worth adding verbage to remind folks on update that the seed is only for new addresses. Originally when adding hd key, we did create a new address, but I think that may have been removed and only occurs in manually adding |
thanks , i gotted it |
🚀 Feature Request
Hi,I am a user of semux,i use the gui wallet in windows.when i want to recovery my lost wallet.data with mnemonic,i found there is no way to recovery wallet from mnemonic, is there some way to recovery my wallet from mnemonic??
The text was updated successfully, but these errors were encountered: