Topic: wallet.dat and co (Read 1236 times)

Hello mocacinno and HCP.

Yes, I have a few wallets => 2014, which means absolutely nothing and the reverse may also be true. I don't remember for my part

The problem I have at the moment on the ten wallets and my few wallets
(6 wallet, 0 encrypted key, 0 decrypted key) found using the "--recover" option ...,
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"

And others just don't work

There should be a search time then possibly: "Warning: root: pycrypto or libssl bit found, decryption may be slow"
Then return to the master command (=> C: \ python27)
OK

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 "


Or:
"Error: root: couldn't open wallet.dat / main. Tu quitting bitcoin and running this again."

I don't understand why it's so complicated. I understand why there are so many different topics here



What must be in my opinion is that the pywallet app is too old for what we ask.
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 ...

Okay so I tried it like this seems to work:
C: \ Python27> python pywallet.py --dumpwallet --wallet = C: \ Python27 \ wallet.dat> wallet.txt.

Then is marked: WARNING: root: pycrypto or libssl bit found, decryption may be slow.

And then :
C: \ Python27>

It must have worked because my wallet.txt file is full.

So I'll enter the private keys, I'll tell you. Thank you

Spaces put themselves on bitcointalk by themselves

basically it is I write the sentence in front of C:\ python27. nothing is happening .
it is rewritten there: C:\python27
and even in front of C:\

It doesn't work. I'm on C: \ python27.
I copy and paste.
I press enter nothing happens.
I am redirected to C: \ python27

it is marked after the correct order:

C: \ Python27> python pywallet.py --dumpwallet --datadir = C: \ Python27 \ wsallet.dat>
wallet.txt
WARNING: root: pycrypto or libssl not found, decryption may be slow
Traceback (most recent call last):
   File "pywallet.py", line 5004, in
     db_env = create_env (db_dir)
   File "pywallet.py", line 1269, in create_env
     r = db_env.open (db_dir, (DB_CREATE | DB_INIT_LOCK | DB_INIT_LOG | DB_INIT_MPOOL | DB
_INIT_TXN | DB_THREAD | DB_RECOVER))
bsddb.db.DBNoSuchFileError: (2, 'No such file or directory - C: \\ Python27 \\ wsal
let.dat \\ __ db.001: No such file or directory ')

 

Yes, voici ce que vous m'avez demandé :
1) C:\python27\python
2) C:\python27\pywallet.py
3) C:\python27\wallet222.dat
4) wallet222.dat

Et le wallet.dat utilisé est dans "C:\Users\user\AppData\Roaming\Bitcoin\wallets

Hello HCP.
I encounter a new problem.
I was kind enough to put to the game ...
Without result, I am not very good at this game ...
Here's the problem :
I correctly enter the command line "--dumpwallet --wallet = pathToTheWallet> outputfile
And so in the output file and more recently in the command prompt,
And I'm told that the "ecdsa" package is not installed ("'edcsa' package is not installed, pywallet won't be able To sign / verify messages") = only output message
I downloaded python38 ar it said it already had the package.
I downloaded "python-ecdsa-master"
And said ecdsa with.

No result...
I'm starting to get a bit long in this topic.
But do you have any idea please mister HCP. I will appreciate it.
In addition we are not very far from the goal "I think"
How to install this ecdsa please sir HCP ??

Well say so it's well explained you took the time ...
If I have anything you will be the first to be notified and paid.
We're going to try that.
I do not guarantee that it will work.
If that doesn't work I'll send you a small paysafecard ...
thanks thanks thanks !!!

By that I mean that I don't have any key found in the wallet. But just one or more "wallets" found in the wallet.dat file.
So, would there be the possibility that there are funds in the wallet.dat file,
where is marked, after the command line
(--recover recov_size 8gio - 'recov_device F: --recov_outputdir outwallet)
that' there should be
wallets, encrypted or decrypted private keys. And that there is "spotted" only "wallet" ...

(6 wallet
0 keys encrypted
0 keys decrypted)
 

Okay.
Thank you for your explanations I already have the hexadecimal software and found the following 32 bytes.
The same goes for the walletdump.
There is a lot of key to import in both cases.
I will do it...
But if I want to import everything with bitcoin core the whole thing, there must be wallets, encrypted keys or decrypted keys?
In this case in with --recover I have numbers in wallet.

Hello.
Yes the pywallet script was wrong.
I sent the files to pywallet where I could find 6 wallets but 0 keys.
It means I have nothing on it ... I'm pretty sure ...

I could try with the hex editor and entered the first 32 bytes? How do you get the first 32 bytes out Please ...

I don't believe they had a password. Or a simple one.
Every time I use pywallet.py and the option - recover I am asked to set a password, but I only put it there ...
The only thing I don't understand is spotted the "first 32 bytes" in the other post ...

Sorry.
I've changed

Hello hcp
You were right I wrongly noted the size.
I found 7 wallets on my USB key. But still corrupt ...>

Regarding pywallet 2.2, it is the site that manages the address and private key we are talking about.
I tried it didn't work but if we manage to make it work that suits me too: P

It reassures me that I have no fear of hack my debug file ....

Have you seen this post 11 file? Could it work?
Below.
https://bitcointalksearch.org/topic/walletdat-corrupt-2012533

...
Here I think this is the pastebin:
https://pastebin.com/SwHLAAQT

Thanks again for your help hcp and the others too

I just retry it is written.
Failed To rename wallet.dat To wallet.dat.16 .... bak
Shutdown: in progress ....
Scheduler thread exit
Shutdown: done

maybe that's another problem?

It's good I found the file in the bitcoin folder. It is marked 1:
Failed To rename wallet.dat To ... wallet.dat.160 ... bak
Below 2:
wallet.dat corrupted, recovery failed

Hello. How do I open the debut.log file without touching the wallet.dat file.
When I type in the bitcoin folder: bitcoin-qt.exe -datadir
the error message is written to me:
Corrupted wallet.

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!


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.


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


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


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.


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".


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!

 Hi, I think i can help with your wallet.dats. How many wallets do you have? Can you send the wallets like you say. I have some technique like pywallet that might work but i cant guarantee. But i could try. If we succeed you can send me fee or reward, i would ask not much. My programs work on damage wallets so it may work.
 Reply back or to my email:[email protected]