For hashcat, there should be sollutions, eventough i've never tried them, and they're probably not a one-click-sollution (but rather a manual setup);

https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_can_i_distribute_the_work_on_different_computersnodes

Like i said: never tried this myself... But it should work...

Did you forget the password of your wallet.dat or do you remember it?

If you remember, then you can skip the process of getting public keys entirely, and open Bitcoin Core andsend the wallet's balance to another wallet.

If you don't remember the password, then you need to understand that wallet.dat files have several hundred private keys inside it and that each one has a corresponding public key and address. You only need the public keys for addresses that have a non-zero balance in them.

You sound like you know how to use tools, so you should run Pywallet with the --dumpwallet switch to get a list of addresses inside. The private keys might be encrypted but that is not a problem for now.

Then, use block explorer like Blockchair to check if 1) the address is in their records - in other words, there is a transaction associated with it - and 2) if any bitcoins have been sent from those addresses. This'll give a compressed public key, but if a tool only accepts uncompressed keys there is a method to convert between the two.

The latter part is important because the public key is only exposed for outgoing transactions. If an address has only received incoming transactions then its public key has not been revealed and you only have a hash160.

P.S. it is far more likely you can recover the wallet if you brute force the password instead of each public key because you might have a faint remembering of the password while you have to search the entire 256-but range for each public key, and it will be almost impossible even for one public key.

You are going to want to make a token file. The instructions on how to do this are here: https://github.com/3rdIteration/btcrecover/blob/master/docs/tokenlist_file.md
See in particular this section: Expanding Wildcards

If I'm reading your post correctly, your token file should look something like this:


This will try all passwords beginning with abc123 followed immediately by either 7 or 8 characters of digits, lowercase letters, and uppercase letters (so only 13 and 14 character long passwords). If you wanted to try every password from 7 characters up to 14 characters, you would instead use: