-
Notifications
You must be signed in to change notification settings - Fork 2.9k
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Trying to recover old wallet.dat #1845
Comments
Not sure if it's being overwritten, if your client isn't synced. First create new addresses and look them up in an explorer to see if they have balance. If they do, dump the keys in the debug window and import in another wallet. If it is being overwritten, you can also import the old wallet while the client is running, from debug window (importwallet path/to/wallet.dat). Look up which addresses have balance, dump the priv keys and import into another wallet like coinomi. |
Hi, I think you can use this script to extract your addresses and private keys: |
Is there anything in the debug.log file to indicate what's happening? It will need to replay the blocks to verify what balance is in the wallet, that's potentially the issue, though? Have a look at https://coinguides.org/rescan-reindex-wallet/ and the |
This happens to my wallet too, I realised that the key pool like 2 keys that are on a different order appended to it and as a result the ones that had been in line are ignored and turn up corrupted |
@SkivvyNivvy @etherx-dev Were you able to solve your issue? |
This comment was marked as spam.
This comment was marked as spam.
No not yet |
This issue tracker is only for technical issues related to Dogecoin Core.
For general questions about Dogecoin please use one of the various communities, e.g. Reddit, IRC, Discord, etc.
Describe the issue
I got my old wallet.dat from an old hard drive from 2017. Whenever I try to have doge coin core use it, the wallet gets overwritten and has a new creation date, a balance of 0, and no transaction history. Is there a solution to this, is there a way to dump my keys from windows cmd? If it were encrypted, shouldn't prompt the passphrase (not sure if it is but I'm pretty sure I have the pass phrase)
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:
Expected behaviour
Tell us what should happen
It should load up the wallet
Actual behaviour
Tell us what happens instead
I replaces the wallet with a fresh wallet.
Screenshots.
If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.
What version of Dogecoin Core are you using?
List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.
1.14.2
Machine specs:
Any extra information that might be useful in the debugging process.
This is normally the contents of a
debug.log
orconfig.log
file. Raw text or a link to a pastebin type site are preferred.The text was updated successfully, but these errors were encountered: