hi guys, I´m Having the same problem. But on litecoin-qt old encrypted and formated wallet.dat (i recovered with Easeus)
Got my old Wallet.dat (72kb)
i installed Litecoin core, i run the updated chainblock. Pasted my old wallet in the AppData/user/roaming/litecoin
And it´s said "wallet corrupted Savaged failed.
I have all lost data recovered (src. daemon, qt blockchain) everything in my Pc.
I read some about Pywallet, but i dont know how to do it.
Please help. Thanks
Topic: Testing old wallet.dats - page 2. (Read 1715 times)
Why does core create a new wallet file every time i insert a new wallet.dat and i end up with one named wallet and the one i inserted named wallet.dat.?
It can get confusing. Each time the core software runs it checks for a wallet.dat file. If one is not present it will make a new wallet and run that one. I rename all the wallets I work with then change the name back to wallet.dat when I put it in the bitcoin folder. Otherwise I risk overwriting a full wallet with an empty one. if you use Winxx you should be able to find your hidden bitcoin folder by running
Code:
%appdata%
Hope this helps.
Hmmm. It should. Are you sure it is the correct folder? It will be the one that core created the wallet.dat folder in. You will have to excuse my ignorance of windows, if that is what you are using. But I sort of recall that windows hides the folder with the wallet but displays another "bitcoin" folder.
Also make sure that the name is "wallet.dat". Anything else will be ignored. If it's corrupted I would expect an error, but maybe not?
Did that help?
Why does core create a new wallet file every time i insert a new wallet.dat and i end up with one named wallet and the one i inserted named wallet.dat.?
It can get confusing. Each time the core software runs it checks for a wallet.dat file. If one is not present it will make a new wallet and run that one. I rename all the wallets I work with then change the name back to wallet.dat when I put it in the bitcoin folder. Otherwise I risk overwriting a full wallet with an empty one. if you use Winxx you should be able to find your hidden bitcoin folder by running
Code:
%appdata%
Hope this helps.
Why does core create a new wallet file every time i insert a new wallet.dat and i end up with one named wallet and the one i inserted named wallet.dat.?
It can get confusing. Each time the core software runs it checks for a wallet.dat file. If one is not present it will make a new wallet and run that one. I rename all the wallets I work with then change the name back to wallet.dat when I put it in the bitcoin folder. Otherwise I risk overwriting a full wallet with an empty one. if you use Winxx you should be able to find your hidden bitcoin folder by running
Code:
%appdata%
Hope this helps.
Remember to backup your wallet.dat's before diving deeper, many a wallet file I have killed due to testing, recovery and otherwise. They can be fickle things. #PrivKeysForLife
Why does core create a new wallet file every time i insert a new wallet.dat and i end up with one named wallet and the one i inserted named wallet.dat.?
No, you only need to sync it to see the transactions. If you load it up and use "dumpwallet" you should be able to get all the addresses and keys straight away.
"salvagewallet" is a last ditch attempt to extract keys from a wallet... it is not recommended unless you have exhausted all other options of wallet recovery... as it can mess up a perfectly fine wallet.
"salvagewallet" is a last ditch attempt to extract keys from a wallet... it is not recommended unless you have exhausted all other options of wallet recovery... as it can mess up a perfectly fine wallet.
So they won't show via file-addresses straightaway?, before sync?. Thanks.
No, you only need to sync it to see the transactions. If you load it up and use "dumpwallet" you should be able to get all the addresses and keys straight away.
"salvagewallet" is a last ditch attempt to extract keys from a wallet... it is not recommended unless you have exhausted all other options of wallet recovery... as it can mess up a perfectly fine wallet.
"salvagewallet" is a last ditch attempt to extract keys from a wallet... it is not recommended unless you have exhausted all other options of wallet recovery... as it can mess up a perfectly fine wallet.
Does it need to sync past 2013 to have the addresses?.
I have 5 old wallet files from the middle of 2013 for bitcoin core. What is the best procedure for trying them out in the latest bitcoin core?.
Should I run salvagewallet straight away or not?, and do I have to let it sync before I can tell whether there are Btc in the wallet via addresses?. Also what is the original command if I want to run it in standard command after removing the salvagewallet command (i forgot what the original was!). Thanks again for any help.
Should I run salvagewallet straight away or not?, and do I have to let it sync before I can tell whether there are Btc in the wallet via addresses?. Also what is the original command if I want to run it in standard command after removing the salvagewallet command (i forgot what the original was!). Thanks again for any help.
I think you should run it with the updatewallet command first.
Once you've done that, just look at the addresses and put them into a block explorer, such as: blockchain.info/address/yourAddress
And see if there's any balance in the addresses.
Running it in standard conditions is just running it normally.
I have 5 old wallet files from the middle of 2013 for bitcoin core. What is the best procedure for trying them out in the latest bitcoin core?.
Should I run salvagewallet straight away or not?, and do I have to let it sync before I can tell whether there are Btc in the wallet via addresses?. Also what is the original command if I want to run it in standard command after removing the salvagewallet command (i forgot what the original was!). Thanks again for any help.
Should I run salvagewallet straight away or not?, and do I have to let it sync before I can tell whether there are Btc in the wallet via addresses?. Also what is the original command if I want to run it in standard command after removing the salvagewallet command (i forgot what the original was!). Thanks again for any help.
Jump to: