is that on my command line:
C: \ Python27> python pywallet.py --dumpwallet --wallet = C: \ python27 \ wallet222.dat,
(Or another (wallet6.dat?)
Some wallets go in the text file
But it is written:
Wallet data not recognized: {'__ type__': 'keymeta', '__value__': "0xc \ x00 \ xea8 .... numbers letters and" \ "...}
"On several lines"
No "hexsec" nor "sec"
That is relatively normal... you'd need to scroll down a LONG way, like several hundred lines to find all the
actual key data... The fact that it is finding "keymeta" data is a
good sign... it means that it is actually a likely to be a wallet.dat file. It doesn't guarantee that it's not totally corrupted or the key data isn't encrypted, but it is a good starting point!
There should be a search time then possibly: "Warning: root: pycrypto or libssl bit found, decryption may be slow"
That simply means that python is missing a couple of libraries that can make it decrypt wallet data "faster"... but are not required if the wallet files have no password. It can generally be ignored.
But not :
"traceback (most recent call last):
File "pywallet.py", line 2111, in parse_wallet
d.update (parse_Blocklocator (vds))
TypeError: NoneType object I not iterable "
This generally happens with "new" wallet files that were updated/created using newer versions of Bitcoin Core... it added some database records to the wallet.dat files that PyWallet does not understand
There are ways around that, but it involves editing Python code, which I feel may be beyond you
Or:
"Error: root: couldn't open wallet.dat / main. Tu quitting bitcoin and running this again."
This happens when the wallet file specified using
--wallet:
1. Does not actually exist
or
2. Is corrupted
or
3. Is already open and "locked" by Bitcoin Core
or
4. Is not actually a valid Bitcoin Core/bitcoind generated wallet.dat
I don't understand why it's so complicated. I understand why there are so many different topics here
Because you're getting into "non-standard" wallet manipulation territory... They were not designed to be easy to just randomly extract data from... they were designed to work with bitcoind/Bitcoin Core... When things go "wrong" and the wallet files get corrupted, things unfortunately become "difficult" if you're not familiar with commandline scripts etc.
What must be in my opinion is that the pywallet app is too old for what we ask.
Yes and no... if your wallet files are indeed from 2014 and haven't been "upgraded" to newer formats by newer versions of Bitcoin Core, Pywallet should work with them "OK".
option: I am ready to find someone I trust to whom I will priest my wallet and others, you never know.
Private message me so that I can see how we do it ...
This is a "Bad Idea"™ You'll likely get a lot of PMs from a lot of dubious characters asking for wallet.dat's and passwords (or asking for TeamViewer/Remote access etc) who'll promise you the earth and then just steal your coins
Be VERY careful whom you trust here!