Bitcoin-core wallet format has changed since 2009 so I think the easier is to export the private keys using pywallet and import them into an Electrum wallet
You can also first export only the addresses to create an Electrum read-only wallet and then check the balances to export exclusively the couple of private keys you need
That would be safer as I guess the 2009 wallet isn't encrypted

C'est bien ce que dit LeGaulois, le mec est spécialiste et doit demander pour savoir que miner du Bitcoin n'est plus rentable en France (depuis quoi, à peine une demie douzaine d'années?)
Même ma soeur qui ne suit pas du tout les cryptos le sait 

Là est justement tout le problème, ils l'ont présenté à plusieurs reprises comme en étant un

Sinon effectivement l'émission est plutôt pas mal vu la cible et son existence fait du bien
Et Raymond n'est pas vraiment un problème, tous les autres en face sont plutôt bons

What are you saying?
Not dead at all? Wallet? Thief? Hack?
The coins have been sent to the first person or bot finding and using a private key such that
RIPEMD-160(SHA256(public key)) = 0000000000000000000000000000000000000000

Ah oui merci

Grégory Raymond

Ca se confirme de semaine en semaine, et les téléspectateurs nous imaginent comme lui...
Heureusement qu'ils ne se rendent pas en plus compte qu'il dit des conneries

Great, I'll let you know!

What is broken always has been broken
Today's fix is about compressed keys not being recovered for example
Recent wallets, like the ones using BIP32 seem to be recoverable at least partially but I don't know exactly what works or not

In case I break more things than I fix though, you can use that 'legacy' version here: https://github.com/jackjack-jj/pywallet/tree/b52c955f8c93a75745166ebf281448016e1f22e2

Isn't there a tool out there to bruteforce a sentence with one bad word?
I think so but if not I can make one quickly

Damn, nice catch, fixed
So many common letters, that should be forbidden!

Good to know bitcoin-core can import BIP32 HD wallets!

In this tool you put your 12 words in "BIP39 Mnemonic"
This will give you a private key in "BIP32 Root Key"
You may need to put your "xc2" password in "BIP39 Passphrase (optional)" too

If it works you can import the "BIP32 Root Key" in Ethereum (I'm not sure bitcoin-core has implemented BIP32 yet) and use your funds

Well the recovery has some bugs but from my tests it finds at least a few keys for recent wallets
Things will be clearer in a few weeks

Hi
I don't know if you can move your thread but the forum for technical help is there: https://bitcointalk.org/index.php?board=4.0
12 words phrase is likely a BIP39 or Electrum mnemonic, try using tools on internet but use them OFFLINE! I just found this for example https://iancoleman.io/bip39/
Your 'xc2.....2om' word may be a password?
And the 80MB wallet may be a Truecrypt/Veracrypt container? (encrypted with password xc2... ?)

Support of Python 3 is started
Basic things seems to be working but you'll likely find bugs

Also the recovery looks broken, I fix a a small part but I'll fix that during the following weeks

This

Do NOT post any unnecessary personal data here

I'm sorry I'm a little confused, this thread is a year and a half old and I don't get if you managed to find any wallet or key
Based on this I guessed not
The 70 only means pywallet found 70 master keys but no addresses at all, this means weird

When were the wallets created? Are you sure it is a bitcoin-qt/core wallet?
BTW I found out the pywallet recovery is bugged, I fix a bit of that a couple hours ago you can try the new version and see if it finds any key

A new 'last resort' feature: the --minimal_encrypted_copy option create a copy of a wallet but containing only the encrypting parameters and one unused key pair
This tiny wallet could then be shared for people to bruteforce it in case of a lost password situation
Obviously not a perfect solution but better than losing the coins

People lose money and see Bitcoin as a scam
And "hopefully" when there is enough lost money people reverse-engineer that wallet and find the derivation path

Thanks for your answers that really clears things out!
Good news is the wallet still controls the money
The bad news is that it's encrypted so you have to find the password, you can't do anything without that
Command to try a password:

You can have two self-explanatory outputs:


Obviously you want the second one
To be clear: the moment you have the "passphrase is correct" output with the hexsec/sec/secret values, this means you have the money back (except for the few more seconds needed to transfer it to an Electrum wallet)
This also means that what you have on the screen is worth the whole balance, meaning that using a photo of it or an eidetic memory a person can steal the coins before you transfer them

Try a couple of passwords with different capital letters, punctuation, space, etc
If you really can't find the correct one: first stop thinking about that for a couple of days and try again, maybe you husband changed some 'i' to '1' or things like that

If you're really stuck then you can use tools to bruteforce the wallet using what you remember of the password, doing modifications on it and other things
Keep in mind though that depending on how well you remember it it may still take centuries to find it
Some examples (that I never tried) you can find on Google:
  https://github.com/glv2/bruteforce-wallet
  https://github.com/gurnec/btcrecover

They may not be applicable for your specific password problem, we may have to make a custom one
Just try for now and come back to report success or failure
Good luck!


Note: "Version mismatch (must be <= 81000)" is just a warning, disregard it

I wouldn't call that a burned address

I meant "handling the non-crashing"
I hope the handling will be done not too far in the future but I'll have to check when the (several?) breaking changes occurred
Also I think many things would be broken anyway but at least as you say people can dump keys, which is 99% of what people use pywallet for I think

New version:

• stop breaking when recent wallets, handling will be done later though, thanks to HCP for handling that with his fork
• add --find_address option: this looks for an address in all the keys of the wallet

Sorry to insist but can you confirm that you see encrypted_keys with pywallet?
I've helped many people and even small misunderstandings can lead to a great amount of lost time

This is not the issue
When created, the wallet file contains around a hundred keys (let's say K1, K2, K3, etc, K100)
Those keys contain keys you can see and some change keys
All are used to compute the displayed balance
When you set a password you encrypt the whole wallet with this unique password, not parts of it so all the initial keys are in there
(One problem can arise when you made around one hundred transactions after the last backup but this doesn't seem to be the case here)

Do you happen to have either the transaction number, the sending address or the receiving address of the big transfer?
Maybe you were actually hacked and this could confirm this

Also I'm confused with this sentence of yours
Are you talking about the same wallet file?
As I wrote above, one wallet has exactly one password
And you say that you were 'able to access the original small change', so that would mean you know the wallet password

You mean from within bitcoin-core right?

If so, using pywallet you can dump the wallet, with all the encrypted keys, right?
Then there is no way around that, you must find the password that was set, maybe there is a missing character of something else but you need to find that out