Quote from: LoyceV on February 17, 2025, 12:22:51 PM

Quote from: Khaledzuhri on February 17, 2025, 12:17:24 PM

13 years ago I bought Bitcoin through a broker and he created a wallet for me on Bitcoin Core
~
How can I access the wallet and recover the password?

I've seen this story far too many times. Brokers don't create wallets for you, brokers send your payment to the address you provide.
My guess is you downloaded (or bought) a fake wallet, and now you're wasting everyone's time, including your own.

I agree. If OP willing to share list of "his" Bitcoin address that have some balance, it's probably either
1. Listed on Don't buy "wallet.dat" files with lost passwords. EXCHANGE THEM!. Note that i don't recommend anyone waste their time to inspect or crack any of those wallet.dat file.
2. Publicly known address that usually owned by exchange, hacker or presumed owned by Satoshi.

And as reminder or new information to all readers, here's detailed explanation by Bitcoin Core contributor about fake wallet.

Quote from: achow101 on April 12, 2019, 02:10:03 AM

The wallet file isn't fake per se, nor are the transactions it shows. What's fake about it is that it doesn't contain the private keys it claims it does.

Quote from: yangxin325 on April 12, 2019, 12:44:33 AM

The method of identification is to look at the corresponding version of the wallet code, check the data consistency, time, field, type, structure, It looks very complicated.

It actually is not that complicated. You don't need to check any data consistency, time, etc. You don't need to check any of the things you mentioned. You also don't really need to look at the wallet code because the data that they are manipulating doesn't change frequently, if ever. In fact, the specific database fields that are being modified will likely never change in order to maintain backwards compatibility with older wallet versions.

What the authors have done here is simply add fields which represent encrypted keys. These fields contain the pubkey and the encrypted private key which will typically just look like random data (because that's the point of encryption). What the authors have done is just create a field that contains the pubkey and random data (or in this case, a string) as the private key.

It is impossible for anyone (technical or not, professional or not) to identify that the wallet is "fake" by simply looking at it (besides the fact that common sense tells you its a scam). If done correctly, the supposed encrypted key will be garbage data and its veracity cannot be determined without knowing the decryption key. Of course, if it's just zeroes or some other obvious non-random data, then it can be easily determined. You can inspect the data of a wallet.dat file using BDB 4.6's db_dump tool.