I understand your frustration that your trying so far to get something out of the wallet file didn't yield any desirable results. Understandably your nerves could be on the edge. You know, it won't benefit you if you insult other forum members. You are the one asking for help and support with your issue.

You may not get always answers that you like. Some experienced users here have seen a lot of shit and react sometimes a bit out of prior experiences. I'm not judging your problem, nor am I classifying it as shit, to be clear. Different users have different perception of presented problems, that's how it is. But friendly advise, if you need help, don't be aggressive or insulting... bad recipe!

I'd suggest: swallow your pride and continue to seek a solution for your problem. You're still far from goal line.

When I read your aggression, I had to think twice, if I should continue to post in your other thread, because I don't like to devote my time to unfriendly users.

Holy moly, this is new to me, thanks for this! I just looked up the short help with bitcoin-cli help dumpwallet (Bitcoin Core v26.0) and there's absolutely no reference to addresstype whatsoever affecting the output of this command. I'm puzzled, need to investigate further.

When dumpwallet is affected by settings in bitcoin.conf like addresstype=legacy, it might be necessary to also specify changetype=legacy for change addresses (for legacy address type here).



I'd rely at such an important verification step on proven tools like Electrum wallet. Your Python script may be OK, but how do you know after just a few tests? Your script may just skip gracefully without signaling issues if it's programmed the wrong way. If you don't understand the code, you can't know what it is doing. I would be careful with "unknown" scripts.

You don't give any details about the script and it's a bit annoying to always have to ask for further details. I mean, you should be the one who is very much interested to be certain to use the right tools, no?


What address type did you get in your output file of dumpwallet command (public addresses of 1... / 3... or bc1q...)?

Are those addresses the result of the suggested dumpwallet command?

If so, you may have to specify which address type to dump because the command defaults to "bech32" if addresstype isn't explicitly set.
Since you do not know the actual address(es), you may have to create a separate dump with legacy and p2sh-SegWit addresses.

To do that, you either:

• A. Close Bitcoin Core, set addresstype=legacy to your bitcoin.conf file, Open Bitcoin Core then use dumpwallet command;
      Close Bitcoin Core, set addresstype=p2sh-segwit, Open Bitcoin Core then use dumpwallet command with different dump file name.
      (Your third option would be addresstype=bech32 if your current dump file has legacy addresses; and the other type, bech32m isn't an option in 2020)
  
      Those two dump files will contain same private keys and amount of 'key & address lines' as your first dump file but will have the specified address type.
  
      Then use the script that you've mentioned above (after you share it so we can check if it's legit) to see if those addresses have bitcoins.
  
  
• B. This wont require another two dump files;
      When you import to Electrum, specify the script types as noted in 'import private key' window's "info" tooltip button.
      Each WIF private key should be imported with different script types to restore all three address types.
  
  e.g. (imports legacy, p2sh-SegWit and Native SegWit addresses):

  WIF_Private_Key01
  p2wpkh-p2sh:WIF_Private_Key01
  p2wpkh:WIF_Private_Key01
  WIF_Private_Key02
  p2wpkh-p2sh:WIF_Private_Key02
  p2wpkh:WIF_Private_Key02
  WIF_Private_Key03
  p2wpkh-p2sh:WIF_Private_Key03
  p2wpkh:WIF_Private_Key03
  ...

  But, don't import too many in one wallet or Electrum may not sync.

Based on your questions you had, I wouldn't place you in the experienced camp. What gives you confidence you did everything right? I ask because you don't give much details.

Are you sure you imported the correct address type (if you imported the private keys in Electrum)?

If you imported the public addresses and you expect to see some transaction history and there is none in Electrum, assuming it synced fully, then either you missed some public addresses or it is the wrong (empty) wallet you exported the addresses from. Based on your "Checked yesterday and It's empty" it could also be that your wallet has been emptied. It's guesswork.

Then carries on to be a "dumb aggressive idiot"

You could import the public addresses into a watch-only wallet in Electrum and you could quickly see if any of those addresses holds any funds. Electrum is a lightweight wallet and doesn't require to download the full or partial blockchain.

If you want to go this way, make sure you download Electrum solely from the official website https://electrum.org/ and verify properly your download file. I'm not going into detail for this as there's an excellent description for that in this forum.

When you have verified that you have funds in your addresses, you could import the private keys of your funded addresses or all private keys of your addresses in a spending wallet in Electrum.

I call bullshit. If you don't remember creating or funding the address and are not the same user of the PC why were you expecting to see a balance and what make a topic when you actually don't see a balance?

In your first post you personalized the entire conversation; "my Bitcoin file", "my PC". And now you switch your story around.

It sounds like it is not actually your wallet.dat file but something you found or bought online, right?  If it is the latter, you have been scammed.

Every client generates a batch of addresses once you create a new wallet, I don't remember exactly the limits but numbers varied from 100 upwards
Have you actually used that wallet for multiple transactions while you were actively using it?
That would explain the generation of new addresses.

I think that you are over-complicating your situation. Like LoyceV said, you definitely should have a backup of your wallet.dat as a safety measure in any scenario, but what you should consider doing after is choose a route of action that is suitable to your needs and current limitations regarding setup. Why are you choosing with the route that you planned when there is an option that allows you access to your funds in a matter of minutes and allows you to see the total balance that is within your wallet (which seems to be your main goal)?

One could argue afterwards the best path to take but for now, considering your first comment, the previous solutions seems rather fit to your current needs.

This should be Step 1 of your plan, not Step 3.


I'm already having multiple copies of the file before doing anything It seems that I forget to say

If you select pruning, your old wallet will require to download the blockchain again. No need for it to download anything if you want to get your addresses only.

 btc core 0.17 didn't ask me also about doing pruined mode and when it done installing I saw on settings that it work on normal one

This doesn't make sense.

- Bitcoin Core requires just 2 GB of RAM, and about 700 GB for storage, which can be reduced by more than 90% if you enable pruning (with pruned=550).
- How bad Internet connection? Downloading 700 GB shouldn't take more than two days, even in cases with very slow download speed.

I wouldn't experiment with my money, if I were you (it is clear that you don't know what you're doing). You used Bitcoin Core to receive the bitcoin, use it again to recover it.