Once I am able to eventually find this file do I just us e a USB stick and move it to a more stable and update device ? that connects to the bitcoin core network or will I able to add that file to another wallet type
again thank you for responding
The 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 |
|
|
|
Je vois pas trop la connerie ou alors la section minage serait beaucoup plus active ici.
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  Perso je ne vois pas non plus en quoi c'est honteux de consulter un spécialiste, puisque lui même n'en est pas un 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 |
|
|
|
All those Bitcoins are not dead at all. They are just lost somewhere in Blockchain locked on wallets and no one thief can hack them. I’m not sure about people’s philosophy towards “burning” BTC. Maybe in such a manner they reduce the number of coins.
What are you saying? Not dead at all? Wallet? Thief? Hack? The coins can be used by the first person or bot finding and using a private key such that RIPEMD-160(SHA256(public key)) = 0000000000000000000000000000000000000000 That's all, just like all other (legacy) addresses |
|
|
|
Ah oui merci Je suis pas sûr qu'il (Musk) soit si fou que ça du Bitcoin [...] faut pas le voir comme un aficionados total, je pense qu'il s'amuse avec nous Grégory Raymond Et la prestation de Grégory Raymond qui est proche du zéro.
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 Edit: et d'après lui Musk n'aimerait pas la SEC parce qu'il a pris une amende pour ses tweets sur Tesla à l'époque, complètement à la ramasse le garçon, il faut l'arrêter Edit2: question sur le minage -> "j'ai posé la question à Gouspillou et sa réponse est claire, non" Et c'est notre expert crypto ça... Cette honte, qu'il retourne écrire sa newsletter sérieux Toute la suite est éclatée mon dieu... Cette émission et son principe sont sympa mais franchement ce mec gâche tout  |
|
|
|
Support of Python 3 is started
Basic things seems to be working but you'll likely find bugs
Also the recovery looks broken, I fixed a small part and I'll fix the rest during next weeks
Sounds like it is coming along nicely... if you get a "stable-ish" release... let me know and I'll do some basic testing on it  Great, I'll let you know! What is broken in recover? I used recently and got a dump fail
Is there a legacy version that is stable that can be reverted to?
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 try that 'legacy' version here: https://github.com/jackjack-jj/pywallet/tree/b52c955f8c93a75745166ebf281448016e1f22e2What do you mean by dump fail? |
|
|
|
Thanks, I've tried that but it says invalid mnemonic. Tried using the password too but made no difference.
Then it's possible that one (or more) of the words is "incorrect"... have a look through that BIP39 wordlist for "similar" words that may have been written down/typed out incorrectly... things like kid, kit, kite etc... 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 Then you can import the two "BIP32 Root Key" (the one with xc2 in BIP39 Passphrase and the one without) in Ethereum (I'm not sure bitcoin-core has implemented BIP32 yet) and use your funds if it works
I'm sure you meant "Electrum" And Bitcoin Core does use BIP32 to generate keys in the HD wallets, and with the advent of "descriptors", you can import xpubs and xprvs... using the importdescriptors command, refer: https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md#bip32-derived-keys-and-chainsDamn, nice catch, fixed So many common letters, that should be forbidden! Good to know bitcoin-core can import BIP32 HD wallets! |
|
|
|
Hi I don't know if you can move your thread yourself but the forum for technical help is there: https://bitcointalk.org/index.php?board=4.012 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/The 80MB wallet may be a Truecrypt/Veracrypt container? Your 'xc2.....2om' word may be a password? Of the container? Or a BIP38 password for your keys? Thank you for your reply, I've no idea what Truecrypt/Veracrypt container is lol, so I doubt that it's that. Furthermore, I don't really understand what this tool you've attached does. I'd really appreciate if you could elaborate. 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 Then you can import the two "BIP32 Root Key" (the one with xc2 in BIP39 Passphrase and the one without) in Electrum (I'm not sure bitcoin-core has implemented BIP32 yet) and use your funds if it works |
|
|
|
|
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 yourself but the forum for technical help is there: https://bitcointalk.org/index.php?board=4.012 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/The 80MB wallet may be a Truecrypt/Veracrypt container? Your 'xc2.....2om' word may be a password? Of the container? Or a BIP38 password for your keys? |
|
|
|
|
Support of Python 3 is started
Basic things seems to be working but you'll likely find bugs
Also the recovery looks broken, I fixed a small part and I'll fix the rest during next weeks
|
|
|
|
Can you post the txid here on the forum?
I don't see why that would necessarily be necessary right now. 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 Found 70 possible wallets
found 0 possible encrypted keys
found 0 possible unencrypted keys The 70 only means pywallet found 70 master keys (wallet encryption parameters) but no addresses at all, this is 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 I'll be fixing this over the next weeks |
|
|
|
A new 'last resort' feature: the --minimal_encrypted_copy option creates 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 $ python pywallet.py --wallet ~/.bitcoin/wallets/test/wallet.dat --minimal_encrypted_copy
Before creating a safe partial wallet you need to check the balance of the following addresses.
You may check the balance on your wallet or using an online block explorer.
Just hit Enter if the address is empty and write 'no' if not empty.
1LKjAaLke66hMdwYgw11nZ2QSaraCjEuRk:
3C7XannaU2cKfQA1hs3a56q63qXng7k8uz: no
1MgjXTP7RMYLD81fNQCyrwHKYgtX3cjjGC: no
1Ed5Bqsfd4mWw3pwv2C8UywGzHWEAMDPJP: no
1947WYGqYYwWWVkBDDppxfQX8Dw2PzqPVb: no
13AdH1Za325jfaYe6vrx5FvUerYn7BpwRX:
3BGxmNSyji5QRzqd9jNnBHPcthvCcoa6Ah:
bc1qzlpyde9m57ur6y58gzqhm37vqmmawp9xcvcvfu:
Are you REALLY sure the 3 addresses above have an empty balance? (type 'YES') YES
Minimal wallet written at wallet.dat.minimal_for_decrypting.dat
$ python pywallet.py --dumpwallet --wallet wallet.dat.minimal_for_decrypting.dat --passphrase 0000
The wallet is encrypted and the passphrase is incorrect
{
"ckey": [],
"keys": [
{
"addr": "13AdH1Za325jfaYe6vrx5FvUerYn7BpwRX",
"compressed": true,
"encrypted_privkey": "ec8125d0304b9f1b40325f005b33b7e2f228b63b22017b64e330cf19b6d089b0e4052174e798a5a30f0229b2338fa368",
"pubkey": "03ffa92cd030c601ec86a959641826292bc5d0bab7ec44d6d6a8935e7ab59fe505",
"reserve": 1
}
],
"mkey": {
"encrypted_key": "cbd9dd630c0ae5b3907294a2a1a6096f00c241850cdce57d49a999c38a96669b72861b9ec9098e19859fa250c9c8f951",
"nDerivationIterations": 136845,
"nDerivationMethod": 0,
"nID": 1,
"otherParams": "",
"salt": "c5f4f5235fa925c6"
},
"names": {},
"pool": [],
"tx": []
}
|
|
|
|
and what happens when they cease to exist?   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, please do it on a PC without internet, especially as you are using Windows: python pywallet.py --wallet=path/to/wallet.py --find_address 1YoUradDress --passphrase "the-password" You can have two self-explanatory outputs: The wallet is encrypted and the passphrase is incorrect
[
{
"addr": "13RhV5gEq5vWXeR6BrqK4tbqre63SSgSTy",
"compressed": true,
"encrypted_privkey": "a6c8a26001dfb1b6fabb73196ead96c7bb0a81c9490e27607dea7b4c0afa5195332136f955103a2 9295e8238079b7d3d",
"pubkey": "031295da558de0efe0dbe904be9748ab44d3b59196079ed4dda6cba889a79d2fc2",
"reserve": 1
}
]
The wallet is encrypted and the passphrase is correct
[
{
"addr": "13RhV5gEq5vWXeR6BrqK4tbqre63SSgSTy",
"compressed": true,
"encrypted_privkey": "a6c8a26001dfb1b6fabb73196ead96c7bb0a81c9490e27607dea7b4c0afa5195332136f955103a2 9295e8238079b7d3d",
"hexsec": "8d1b71624b7bf8d5165cb9c77bea710173219b813da7c9ebc42a1997ad1064fe",
"pubkey": "031295da558de0efe0dbe904be9748ab44d3b59196079ed4dda6cba889a79d2fc2",
"reserve": 1,
"sec": "L1x1EXNCt2mavzE7zT7Vrck57UfZFY8zHuEgcKaQFCknm3ztAGke",
"secret": "8d1b71624b7bf8d5165cb9c77bea710173219b813da7c9ebc42a1997ad1064fe01"
}
]
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/btcrecoverThey 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 And yes, as HCP said above, keep copies of the original files |
|
|
|
1BURNED4fBBJPNBUzytg6Q3HVj7uFGBxNE
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 with 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
$ python pywallet.py --wallet=path/to/wallet.dat --find_address 1Mp26TFhkmyupEFbnuitvTeu8PSiqku6pT --passphrase aaaaaa
[
{
"addr": "1Mp26TFhkmyupEFbnuitvTeu8PSiqku6pT",
"compressed": true,
"encrypted_privkey": "45421e5f31d614803dbdbd1419b6c0fb5cacf61d3a371de637afa3b8c502ae4fc5c674d0421dcf3f246265f6ecae0f81",
"hexsec": "2a26e47fda8e7a0a345f6e4e4da2afa88ee2b69b57eb468911cf73da448f0bcd",
"pubkey": "02008fa3d569d00ac7ae31edbc3cc3f99a59b4e9ee21ae37af8dfe3d50319747b7",
"reserve": 1,
"sec": "KxdeaXTuE7ZVKX92AzPCaiLfnNwYQeSWrrrGsrXYW5y34v6BMiQB",
"secret": "2a26e47fda8e7a0a345f6e4e4da2afa88ee2b69b57eb468911cf73da448f0bcd01"
}
]
|
|
|
|
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 The issue is that the password that was set worked to access the smaller amount within the wallet, but not for the larger amount in the wallet. 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 hidden change keys All are used to compute the displayed balance When you set a password you encrypt the whole wallet with this unique password, 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? (check but don't write it here) Maybe you were actually hacked and this could confirm this Also I'm confused with this sentence of yours We were unable to use the password created on 1/1/2021 to access the larger amount that had been received back as change on 1/7. We have tried multiple combinations of passwords since. We have done the Python method, but since the password isn't working we can't access the private keys Are you talking about the same wallet file? As I wrote above, one wallet has exactly one unique password for all the keys And you say that you were 'able to access the original small change', so that would mean you know the wallet password Another questions When was the wallet created? Encrypted? What is your bitcoin-core version? What is your OS, Windows or Linux?
Last thing: This may be about a 'change addresses'-related bug triggered on old wallets If you know the address that received the 'lost' funds, look for its info with this pywallet (download the new version, I just pushed it!) command output python pywallet.py --wallet=path/to/wallet.py --find_address 1YoUradDress , if there is no output then answer all my previous questions and don't read below If it is there though you should have the key (if hacked then the coins would be gone though) The output should look like this: {
"addr": "13aLG7bQrokjmwpjSTV252MAUVFSvSTdvJ",
"compressed": true,
"hexsec": "aec3301d51faa7c31b8fd6a7eb902f3ccfdd5d4a4491a088004a03b260901a37",
"private": "xxxx",
"pubkey": "020017ebde6ec0ca2c76324d96c725f26fd66b331f02e1f3033d7e639058537836",
"reserve": 1,
"sec": "L35RgAh2euE8Q1pLEaA2ERsH6D9QEcQGK1mDwxZkg3ir3tco8Anq",
"secret": "aec3301d51faa7c31b8fd6a7eb902f3ccfdd5d4a4491a088004a03b260901a3701"
}
What you need is the "sec" value, this is your private key (here for the 13aLG7bQrokjmwpjSTV252MAUVFSvSTdvJ address) If you have this instead: {
"addr": "13aLG7bQrokjmwpjSTV252MAUVFSvSTdvJ",
"compressed": true,
"encrypted_privkey": "7e77381ea8764ca899599dc47ad8e4f135188b482ffa2f7bdc6f174c920ebca4ab8716f890cc2da65de139c5f280711c",
"pubkey": "020017ebde6ec0ca2c76324d96c725f26fd66b331f02e1f3033d7e639058537836",
"reserve": 1
},
This means that you must specify your password by adding the `--passphrase your-password` option to the command line and you'd get the "sec" value as expected (consider this insecure though so you should change your password afterwards, but let's focus on recovering the private key first) If you can't get the "sec" value of your address, then come back here to tell us what errors you encounter and post them (without sensitive content though) If you can get the "sec" value then just download the Electrum wallet, import the private key and check you see the balance ( https://bitcoinelectrum.com/importing-your-private-keys-into-electrum/ ) DO NOT SHARE ANY OF THE "sec", "secret", "hexsec", "private" OR "encrypted_privkey" VALUES! |
|
|
|
He put a password on the wallet and made copies 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 There is no password corruption possible and this thing is robust, you 'just' need to find out the real password If you can't, there are plenty of fuzzers around here and I think that if you are only a few characters away from the real password it will be recoverable |
|
|
|
|
Show Posts
