The error may be logged before you opened bitcoind with reindex, have you experienced the same error after -reindex?
Yes you can, there's nothing in the debug log that can compromise your private keys, only some privacy-related info.

• (CMIIAW) I think you can delete the last block file and Bitcoin Core will detect it and issue -reindex then it will sync starting from the last valid block.
  However, if your blockchain is pruned, it will sync from start if you do that.
• Yes, but not just the blockchain, if you're going to back it up, you may as well backup the whole data directory.

If the error persist after reaching the height where you've encountered the error, your blockchain may have been corrupted by the sudden shutdown.
If so, you can open your "debug.log" file from bitcoin data directory (default location) to check for errors related to the corrupted block or for possible other issues.

If there's no error and you've reached the tip of the blockchain, then it's good.

Or use BTCRecover instead?
It has a seedrecover.py script that can bruteforce your 2 missing words; however, you'll need to provide an address or the master public key as reference.

Links:

• btcrecover: https://github.com/3rdIteration/btcrecover
• seedrecover quick start guide: https://github.com/3rdIteration/btcrecover/blob/master/docs/Seedrecover_Quick_Start_Guide.md

Use restore instead of create.
Example:
Enter the wallet name after the "-w" argument, and the private key(s) (with script type) after "restore".

The good thing is, there actually is a setting for that (start parameter or bitcoin.conf entry):
maxtxfee = sets the maximum transaction fee in BTC that your node can broadcast/relay,
The default is 0.1BTC, still too high but at least it can prevent >1BTC disasters.

Bitcoin-qt - 'Help->Command-line options', under "Debugging/Testing options:":

Test the "-l" argument first to see if your GPU is supported:

If yes, you just have to add the argument -gpu when searching for a vanity prefix.

No, a well-written client/wallet will send the remaining amount to your 'receiving address' or back to the same address if 'change address' is disabled/not available.
It will only happen if you will create the transaction by hand and forgot to specify a change address, eg. through Bitcoin Core's createrawtransaction command.
I haven't heard of a wallet that fails to do that and forgot to claim the remaining balance from the UTXO.

Try to add server=1 into your bitcoin.conf file.
If it didn't worked, please provide some lines from Armorylog.txt that may be related to the issue.

Actually, this isn't because of the change address but because 'Bitcoin Transaction' is "UTXO" based (more info).
Each unspent transaction output in the blockchain should be spent whole so if you need to spend one with the huge amount, you'll need to send the excess amount to another address in your wallet
which is usually sent to a 'change address' but can also be sent to a 'receiving address' depending on the wallet.
So even if you disable change address, the rest of the amount from the UTXO that you're spending should be sent to an address;
Otherwise, it will be added to the transaction fee.

Your wallet is making you wait for confirmation, it must be because it's set to wait for confirmation before spending a UTXO (the change of the unconfirmed transaction).
Some wallets have a setting to be able to spend unconfirmed unspent transaction outputs.

It should have a fee setting there... anyway:
My reply is based from your replies to the earlier responses,
I've taken in consideration that you initiated those two transactions, the receiver have received the bitcoins and each transactions used your full balance at that time.

If everything checks out, then it's about the fee (but I didn't get what your last reply is all about).
If not, then it's the "other verdict".

I didn't mentioned anything about the app assigning address by itself, where did this came from?
Is the receiver's address different than the "assigned address" in those two transactions (that you've initiated)?

---

Language barrier, perhaps? Try the local boards: https://bitcointalk.org/index.php#5

That's news.
I know that synchronization is I/O extensive, but HDD/SSD shouldn't fail that easily unless there's something wrong with the hardware.

Have you set the dbcache (database cache) to an insane value that your RAM can't handle together with the OS's background processes?

The seed phrase is enough to restore the wallet.

The steps are simple, just follow this:

• On the 'Install Wizard' of Electrum, select "Standard Wallet" (for the 'usual' wallets) or "Wallet with 2-factor authentication" (for 2FA wallets).
• Click 'Next', select "I already have a seed", paste your seed and Electrum will automatically detect the correct derivation path.
• Click 'Next', finish creating the wallet by typing a password.

If you already created a wallet, you can access the install wizard using the menu "File->New/Restore", then type a wallet name.

The fee was set to 54.398 sat/B on the last transaction which is equals to 0.00010390 BTC when multiplied by the total size of the transaction.
So, that will be deducted from the input together with the sent amount which may be equals to your balance.
It may have used all because the 'change' would have been "dust" (for privacy and to save fee later).

If you do not want this to happen, you should avoid extremely high fee, set it to "Economic" since the normal setting seems to be over-estimating most of the time.
Fee setting is in the "Menu->Fee" when sending funds.

Take note: the wallets listed in bitcoin.org/en/choose-your-wallet aren't developed by bitcoin.org.
Those are just list of Bitcoin wallets to help the end-users to select a wallet based on their preference.

If you're thinking about somehow "recovering" the funds though the developers' intervention: it's not possible.
No one is in full control of the network, even satoshi himself.

What you should focus on is to find your correct funded addresses first, then find their private keys.

For the past and current reference client developers, you can find them here: https://github.com/bitcoin/bitcoin/graphs/contributors

Who is this "sender"?
Someone you don't know, your "friend" or a legitimate service where you can buy Bitcoins?

You must be sure that you've actually received Bitcoins because recovering something that's non-existent will just waste your time.
And as other have mentioned, those addresses didn't received any coins (neither Bitcoins or Altcoins).

Since the thread is not in a specific wallet software board, I assume that you're referring to Bitcoin Core.

There's a workaround but it involves using iancoleman's BIP39 tool and will not work with "Descriptor wallets".
For reference, here's the steps (Air-gap machine is recommended):

• Use dumpwallet command to export your wallet's "extended private master key" [dumpwallet]
• Open the dump file using a text editor to view the 'extended private master key'
• Launch iancoleman's BIP39 tool [github.com/iancoleman/bip39]
• Paste the 'master key' to the BIP39 tool's "BIP32 Root Key" input box.
• Select "BIP32" under 'Derivation Path' for legacy addresses or "BIP141" for Native SegWit and P2SH-SegWit (select the correct script), then change "BIP32 Derivation Path" into m/0'/0' or m/0'/1' (change addresses)
• Tick "Use hardened addresses" under 'Derived Addresses', then toggle: "Private Key" and "Public Key".
• Scroll down and type 1000 (addresses) to "Show" and 0 to "starting from index" input boxes, then click "More Rows".
• There's you'll have a list of 1000 addresses derived from your master key, you can use the "CSV" tab on top if you want to export the list.

Then use the list to create a watch-only wallet.

It's far from a custodial service though, because TrustedCoin doesn't have access to his funds since they only have 1 master private key in their server.
For full custody of the funds, it's still in the user's control since the two master prvKeys and the master pubKey (of Trustedcoin's key) are in the seed phrase.

So I can agree with hosseinimr93's first suggestion to jotaemeese, only if he still wants to use 2FA
and willing to pay for their service (which I don't think he's aware of).

Okay, so I assume that the Multibit wallet backup is corrupted then, because you wont get that error in Electrum with any other private keys aside from the four mentioned above.

There's no shortcut to this since the entropy (128 bit number) needs to be a 'UTF-8 normalized' mnemonic before you can get the 'binary seed'.
You'll need to do the above to convert it into a mnemonic, then use the result to your code.

The service has quite the reputation and the user has positive ratings as well: walletrecoveryservices
There's also a link to their 5-star Trustpilot review page: https://www.trustpilot.com/review/walletrecoveryservices.com

For the data, it depends on what they'll ask you but the whole portfolio plus a list of possible passphrases should be enough.