Chances is, your father meant he has "50000 BTCP".
Anyways, looking for his backup is still worth it.

And speaking of backup, any of those Electrum variants (One for Bitcoin, two for Altcoins) requires a "seed phrase"
to be written as backup before the user can finish creating his wallet.

So look for papers with words written on it (12 words by default) which should be the seed phrase that can restore his wallets(s).
If you found it, get an offline PC, install Electrum and go restore it via "Standard->I already have a seed" option.
Check the addresses (View->Show Addresses) if any has balance.

This should bring a closure to your doubt.

	Screenshot from version 4.3.4:	Screenshot from version 4.4.0:

Both do not display the inputs.
At first, I was wondering if you're talking about the transaction preview when sending bitcoins
but when I checked, it's the same as the screenshots above.

I'm assuming that you took OP's "MPK" as 'Master Private Key'.
Because otherwise, IanColeman's BIP39 tool cannot use his 'Master Public Key' and derive addresses from it.

Seems like the issue was the new hardened derivation path scheme which uses "h" instead of " ' ".

Your solution is kind of insecure since you've used non-hardened derivation paths for the "purpose", "coin" and "account" level which should be hardened by the standards.
If you're planning to use the wallet where you'll create a signed message, use this derivation path instead: m/44'/0'/0'

That loading error isn't related to being an altcoin wallet.dat, it simply means that the wallet is corrupted and cannot be remedied by Bitcoin Core's salvage attempt.
Additionally, even altcoin wallets could be loaded to Bitcoin Core but or course, altcoin transactions wont be scanned.

This is part of BTCRecover's test codes, specifically these lines from the original repository: github.com/gurnec/btcrecover/blob/master/btcrecover/test/test_seeds.py

---

Transactions will be automatically loaded as long as you're online once the correct wallet is restored with the correct seed phrase and extension (passphrase).
I recommend you to make a separate topic regarding the MultiSig wallet since its recovery is different than a single sig wallet with extension.

AFAIK, --recover will restore a "recovered_wallet.dat" regardless if it successfully found any private key.
The difference is if it's empty, it'll result with a non-useable recovered_wallet.dat file without any keys in it.

Recover command should tell you if it found any keys or encrypted keys (plus if those are successfully decrypted)
from the drive you've selected.

Okay so the wallet.dat files are recovered from an old drive (deleted/wiped?)
Getting corrupted wallet.dat files are common in this scenario specially if the drive has been continuously used after the data you're trying to recover was deleted.
This is because those files may be overwritten by the operating system's normal operation or other data that you're writing on it.

Unfortunately, data recovery isn't my expertise and you might need an expert to recover your files intact.
The best suggestion that I can give is to leave that drive unplugged until you found someone qualified for the job or until you've researched enough about data recovery.

bitcoin-wallet tool usually returns with that error if the wallet.dat is corrupted beyond repair.
This is supported by my guess in pywallet's error which is also caused by a severely corrupted wallet.dat file.
I'm afraid that the data is too corrupted for salvage or pywallet.

The only option that I know that may still work is --recover which is designed to look for deleted data similar private keys from a directory.
But you wont be searching for deleted data, it's the data inside your corrupted wallet.dat.

Here's the "general" steps: http://bitcointalk.org/index.php?topic=5408068.msg60653031#msg60653031
If you need more info, read the next few replies since the OP in that thread asked for further instructions as well.

Basically, you'll need to paste it in that drive, preferably empty;
Then using the provided command, let pywallet look for private keys in that drive which the corrupted wallet.dat might still have.

If pywallet can't find it in your specified directory, it'll return with this message instead:
"ERROR: wallet file 'T:\\wallet.dat' can't be found"

Save it anywhere but take note of its absolute path,
for example, if you saved it in "D:\new folder", the wallet.dat's path is "D:\new folder\wallet.dat"
Use that as --wallet path when using bitcoin-wallet.exe tool.

If you didn't changed Bitcoin Core's install directory, bitcoin-wallet tool should be in your "C:\Program Files\Bitcoin\bin" folder.
To use it, open command prompt, "change directory" (cd) to the folder above, type: cd C:\Program Files\Bitcoin\bin
Then to salvage, type: bitcoin-wallet --wallet="D:\new folder\wallet.dat" salvage
Of course, change the wallet's path to your wallet.dat's location.

The rest of the info should in the link on my previous reply.

By the way, the "13 word" is just an Electrum seed phrase with a "Passphrase" which is the 13th word.
When using seedrecover, you'll have to create a list of your possible passphrases (13th word / extension) on a text file referenced by --passphrase-list

You either need your "address" or "master public key" to be able to check if any of those words is the correct passphrase.
That's because any "extension" is valid but a different word will produce a different wallet.

"seedrecover.py" tool of BTCRecover can definitely help you with it, however, it still depends on what you can remember or the complexity of your backup.
Can you make an example of how it looks like? Use random words in your example, do not post the actual backup.

For seedrecover setup, you'll need BTCRecover: https://github.com/3rdIteration/btcrecover
It already has a guide.

Then based from what I understand from the OP, you'll have to combine a valid seed phrase from your words and pick a valid passphrase.
You'll need to provide these arguments:
--tokenlist can be replaced with --seedlist if you think one of the listed phrases is already the correct seed phrase.

Seeing the phrase "ton of phrases" made me think that you'll gonna need it.
For that, I'd recommend you walletrecoveryservices.com which has a good standing.
Also, you wont have to pay a fee right away, only until the job is done.

Check if you can discover the cause,
However, I'd not recommend to submit it as issue to GitHub since it's for an old version.

Enable debugging in "Tools->Preferences->Write logs to file", restart Electrum.
After reopening, reproduce the issue and then find the logs in: <your_electrum_data_directory>/logs folder.
The default Electrum data directory in Windows10 is in %appdata%/Electrum (paste it on your "Windows Explorer" or "run" window)
Open the log file with a text editor and check if there's any error related to the issue.

Don't forget to disable logging later or Electrum will produce a log file in every session.

If you need inbound connections, add -listen=1 command line option or follow the suggestion above, in your "bitcoin.conf" file.
You'll need it since -proxy disabled listen.

Take note that onlynet=onion will prevent you from connecting to nodes on clearnet.

Have you tried in bitnodes if your node is reachable?
If it is now, you'll eventually get inbound connections after a while.

There's an "onion" column in the result of -netinfo so I guess you're already running with -proxy=127.0.0.1:9050 and a Tor onion service...
If so, just follow the third option in this article about connecting via Tor: https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md

I recommend that manual setup since it's the most simple, just add line to your "torrc" file, start Tor, get your external IP from the "HiddenServiceDir" that you've set
and start Bitcoin Core with your correct -externalip and suggested command line options and your node will be reachable via Tor.

You can use: bitnodes.io to see if your node is reachable. (paste your -externalip)

Electrum doesn't support importation of Uncompressed WIF Private key with P2WPKH-P2SH script flag because it's non-standard.

Does your address starts with '1', '3' or 'bc1'?
If it's '3' and "p2pkh-p2sh" is specifically written on your backup, then I'm afraid your issue is more than just importation of the private key
but spending its bitcoins since mostly all nodes will reject transactions that you'll create.

Additionally, I'm not aware of any wallet that derives SegWit addresses from uncompressed WIF PrvKey.

If it's '1', then import it without "p2pkh-p2sh:" and it'll let your click the next button.

Those settings are moved to the settings icon in "New Transaction" window. (After clicking "Pay..." in the 'Send' tab)
For "Advanced Preview", just click 'Preview' instead of 'OK'.

Reference image:


Now, you can edit those settings without going though the 'Preferences' or 'Advanced transaction preview'.

Yes, in standard wallet.
Electrum will have to decrypt the encrypted key in order to sign transactions, thus, exposing it for a brief moment.
And it's not limited to transactions, other options like creating a "signed message" will require access to the keys as well.

"Exposed" as in it's temporarily saved in your RAM, not literally exposed.
For it to be compromised, your machine still needs to be compromised by a hacker, virus or malware; if you have a good security, it wont be an issue.

Use cold-storage set-up to be safe from those security risk: electrum.readthedocs.io/en/latest/coldstorage.html

For other wallet types:
"2FA wallet" requires 2 signatures, only one will be exposed when sending transactions so it's not enough to get your bitcoins stolen.

If you're using the GUI, you can set it in the "Welcome Screen" where you've initially set the data directory and other settings.
To launch Bitcoin Core with it, start Bitcoin-qt with the command line option: -choosedatadir
The advantage of this is you don't have to use a specific shortcut with the -datadir command line option.

Here's a simple guide to do it:

• Go to Bitcoin Core's install directory, it's in "C:\Program Files\Bitcoin" by default. (copy the path for the next step)
• Open 'Command Prompt' (use search if you can't find it) and 'Change Directory' to the dir above using the command: cd "C:\Program Files\Bitcoin"
• Then start Bitcoin Core's GUI with the said command line option using the command: bitcoin-qt.exe -choosedatadir
• The Welcome Screen will open where you can set the datadir.

Take note that your old data directory wont be automatically moved to the newly set dir, you'll have to manually move everything in it.

If you actually asked how to create a watching-only wallet from your Bitcoin Core,
I would've been suggested you to get the descriptor's extended public key right in the first reply.

Good that you've discovered watching-only wallet by yourself, and "Blue Wallet" is quite a good option, IMO.

Right after that, try to send from Bitcoin Core where you got the xpub key.
It's to make sure that your setup works before sending more bitcoins into it.

Bitcoins cannot be mined with GPU at today's network difficulty, just wait for your SHA256 ASIC to be shipped.
Your only option with GPU to earn bitcoins is to use something that mines Altcoin but payouts in Bitcoin. For example: Nicehash
(DYOR in Mining (Altcoins) board)

Update: Version 4.4.0 just got released.

The new GUI looks good and smooth; however, the feature that we're expecting to manually edit the fee or fee rate still isn't there.
Guess you're stuck with 'Static 'slider's 1, 2, 5 ,10 ,20... sat/vB pre-loaded fee rates.