Try to look for a related topic in this board: Bitcoin Forum > Other > Archival > MultiBit

Be wary of users who'll try to help you through personal message, do not share any info specially "keys";
and keep the discussion public as much as possible.

I believe you can extract your private keys from Multibit Classic but I haven't used it so I pointed you to the correct board.

5x10 with three colors... Maybe you're supposed to take the SHA-256 hash of the images and use the hash as a private key.

Also, it looks familiar, not Bitcoin-related but for an old game, but I can't remember which.

The "checksum" that was mentioned in the first post and had been mentioned repeatedly is the keyword.

Without going technical and disregarding the Base58 decode part:
It's basically the last few characters of the WIF private key, that was created by hashing the other parts of the prv key and it's inserted at the end as a the checksum.
So changing a character from the first few characters of the private key will produce a different hash that will mismatch with the checksum.
Or changing a character from the last few characters (checksum) will make the checksum different than the hash of the rest of the characters.
A mismatch means an invalid WIF (Wallet Import Format) private key.

The logs seem normal to me aside from some font issues and "Unknown wallet record: 1" probably because it's an old wallet file, usually not an issue.
Are you sure that it's the correct wallet.dat or the latest backup of it? Because an outdated copy of a non-HD wallet (since you said its old) won't be able to recover the newer keys generated by the active instance of it.

The size is probably because when it's loaded in the latest Bitcoin core, its keypool was pre-loaded with thousand more keys, while the old version only contains hundreds.
The address format, it's because Bitcoin core will generate native SegWit by default but it won't change what's already used by the wallet.
For the encryption suddenly removed, it strongly suggest that it must be an older backup or a totally different wallet.dat than what you're expecting.

Here, I've created a very simple pull-request: https://github.com/spesmilo/electrum-web/pull/11 (Slideshow punctuation inconsistency #11)
I have also linked this topic so the devs will see your actual report  

If you're still using Windows7, open command prompt to Bitcoin\daemon where bitcoin-wallet.exe is located (change the directory if you're not using the default).
For the default wallet 'wallet.dat', this command should work:
For other wallets, use NotATether's command.

Note: It will not return with a response (aside from errors), you can check the data directory and a backup of the wallet will be created upon using the command.

---

Use:

What do you mean by "make it not pay"? You haven't deposited yet?
In freebitco in, you can put a default withdrawal address in your profile which is tied to the account and can even be used to login.
That's one of the options in their instruction, you can sign a message using it unless it's a custodial service or exchange's deposit address.

If you didn't set one, it will default to a random address which I believe they have the control.
That will leave you no option.

No, the only way to see an address' public key is check the "unlocking script" of a transaction that used it as an input (or if you have the private key of course).
So, have you used that address to send bitcoins even once? Inbound transactions do not count.

Try to use "Rescan balance" in Armory: it's in the menu "Help->Rescan Balance", close Armory and it will try to find your walet's transaction(s) from its database.

But before any of that, are you sure that Armory is now sync'd to the network?
If it is, there should be a "Connected (xxxxxx blocks)" on the lower-right hand side of the client.

If not, you may have to post the logs from %appdata%/Armory/Armorylog.txt
eg. default Armory data directory for Windows: C:/Users/<your_username>/AppData/Roaming/Armory

I'm pretty sure he's aware of it  ←_←

"Standard" means that most clients do it the same way as the others.
Which in the current case, signed bc1 address from Electrum can only be verified using Electrum (or other specially-tweaked tools).
The message was signed in a Electrum-specific way.

You can follow this issue: /bitcoin/issues/10542 (Signmessage doesn't work with segwit addresses)
Latest posts are just hours ago.

One reason is you/they may have set a very low fee rate that most nodes had dropped it from their mempool upon reaching the set/default maximum size.
That includes the mempool of your wallet's node or server for SPV clients.

Note: it only happens when there are too many transactions in the mempool and due to the limited space, the node has to drop the ones with the lowest fee rate.

Most users here use Electrum (including me) and no one have encountered "theft" from a verified legit client.
The replies aren't negative in a degrading way. It's just you didn't provided enough info in the first place so most replies became wild guesses.

Lets pile some more things to test/do:

• 1. Try to check the "Addresses" and "Coins" tabs for frozen coins or address, to enable the tabs, click "View->Show Addresses/Coins".
  Frozen address has a blue highlight on the entry in the addresses or coins tab; while a frozen coin's highlight is under the "output point" in the coins tab.
  
  
• 2. The previously set fee rate may be too high that it's registering '0' as your maximum sendable balance since your current balance is just 0.00046975 BTC which can be all used as txn fee,
  try to put the lowest possible amount 0.00547 mBTC in the amount, click "send", set the fee slider all the way down and cancel that send dialogue.
  Now try another transaction but click "advanced" and set a reasonable fee, you'll see a real-time info based from what you've set.
  
  
• 3. You must verify your Electrum, downloading it from the official site doesn't mean you have a legit version. Here are the steps: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/
  
  
• 4. Also, please click the 2fa icon on the lower-right hand side of Electrum (Blue shield icon) and see if you already have prepaid credits in your Trusted coin account.
  It should be written like this: "Your wallet has xx prepaid transactions". If you didn't have any, consider disabling 2fa before sending your bitcoins.

Maybe your wallet has just opened or it wasn't open when you tried to receive the lightning funds?

FYI, you need to be online to receive lightning funds, or was it online?:
If you're not using the new "trampoline channels" (kangaroo icon in the channels of 'lightning' tab), you/your buddy have to keep Electrum open for a short while to fully connect to the rest of the LN network (see the lightning icon's percentage on the lower-right).

This is a separate issue than your other "not enough capacity" thread right?

In Electrum? I think keeping it open will not contribute to the network since Electrum-made channels (trampoline or not) don't route payments (CMIIAW).

Anyhow, it's best to keep your channel(s) open in case you need to send more lightning funds, and also if you still don't need the funds onchain.

You're welcome.. but,
that's not what they meant by saying "offline", you should've saved the page in your disk and launch that on an offline machine... anyways,
the coins has way smaller value than BTC, I just hope that you've already sent your Bitcoins from the addresses of that seed phrase before extracting your BTG.

There's an easier but riskier way aside from the above.
All you have to do is to use TrustedCoin's 2FA Recovery tool (from Electrum's 2fa service provider) and it will generate a ElectrumG-supported 2of3 multisig wallet file.
Then you can simply open that "wallet_recovered" file using ElectrumG.

The catch is, you'll have to paste your seed phrase to that tool.
If you're interested: https://trustedcoin.com/static/recover/standalone.html (please read the warnings)

There's a limitation, it will only show addresses that were previously used by the wallet, you'll likely see the involved (unverified) transactions in the "Transactions" tab anyways.
You can paste their TXID on a multi-coin blockexplorer like blockchair.com to check if those are valid in an altcoin chain.

The only reliable way to check the balance is to sync those wallets to their respective networks, because you'll never know if it's an older backup and the wallet was used a few more times after the "Best block at time of backup" of the recovered backup/file.

I'm pretty sure he meant the "notify" command based from the "notifying URL" and also from his previous posts.
You can find it in the GUI's console's help() command.

I take you're using CLI since it's labeled in the GUI.
Using the command listaddresses, all you have to do is to add --change argument to list the change addresses and --receiving to list the receiving addresses.
Eg.:

For the limit, I think there will be no limit as long as you keep on using the change addresses, it will produce more if the last one was used.

---

I can't comment on Q1 since I'm not using notify().

Rebuilding the database wont take that long and wont cost you any bandwidth.
At worst it'd take about a day or hours to complete depending on your hardware, you should also consider increasing your "dbcache" setting to speed up the verification.
Before starting Bitcoin core: find/create a bitcoin.conf file in the default data directory and add a line dbcache=size
(size = depending on how much RAM you're willing to spare).