You have to be at least a Jr. Member to post images. While you are a newbie, they will appears as links. After you become a Jr. Member they will automatically display as they normally should.

Next time, please use the search function of this forum. This question has been asked thousands of times already.

That's a known bug and should be fixed in the next version, 0.95.

The money is not lost, as the transaction has confirmed.

Just go to Help > Rescan Balance and follow the directions of the dialog. It will rescan the blockchain for your balance and you should see the Bitcoin there.

That is not an encrypted message, which is what OP is asking about. That is a signed message, they are different things. Electrum has the option to encrypt/decrypt messages right under the option to sign/verify them. They are two completely different things.

OP, can you show a screenshot of what you are entering?

Interesting. Try opening an issue on the github page. Also, have you tried using the new ARM builds?

The 76a914...88ac is the standard form for a pay-to-pubkey-hash output script. When you sign a transaction, the output script goes into the scriptsig, hence that format there. You will notice it down below by the outputs.

As for what Electrum is doing, I'm not sure, It doesn't seem like it should work, my best guess is that it's something internal to help it figure things out. I suggest taking a look through the source code (https://github.com/spesmilo/electrum) to see what is happening.

Don't know yet, it isn't really a priority right now.

For you, it should be %appdata%/Armory Delete the folder named "databases" and then start Armory.

Phone home code is any code that communicates back to a server controlled by the developers (i.e. it phones home).

That is the link. All releases will be announced there with links to the downloads.

Working on it. It will likely be available in 0.95.1. If you want to help with that, we have a Transifex project open at https://www.transifex.com/bitcoin-armory/public/. You can help translate the project to another language.

Yes, the database format has changed so it is both much faster to rebuild and rescan and much smaller than the original. You should delete the old databases to free up a lot of space (several 10s of GBs). If you delete the databases folder inside the data directory, it will remove the old databases and the new ones, but don't worry, the new ones will be rebuilt very quickly.

No, that is how it is supposed to be. The updater stuff was removed since the announcements server is no longer working, the development has changed leadership, no announcements server is set up that we can use, and we don't want any phone home code. It may be reintroduced later if we decide to.

If those two words are words in a dictionary, then it is significantly easier to crack since dictionary attacks are very easy to do. However if they are not or are in a different language than english, then the difficulty for cracking goes way up. Even with word mangling and some extra numbers or special characters, the password could still be vulnerable to a dictionary attack.

That's hard to say, especially without knowing what the password is.

In that case, it also depends on the encryption algorithm. Also, since you are reusing the password, if it is compromised in one place, then the time to crack it somewhere else is 0.

Bump.

If both your email and your Bitcointalk are hacked, then the 24 hours doesn't help you at all. You won't be able to access your email either so you can't fix anything.

That is not a good idea. What website takes 24 hours to update an email address? There are very few cases where this would be useful at all. It provides no security to do that, and may be even more insecure. The security is in requiring users to confirm that they are changing their emails, not having to wait for the change to happen.

You'd be surprised, but you really shouldn't be. A lot of people use the same password or some variation of the same password. Once you know one of them, you can get the rest. Common word mangling makes that very easy. Just google it, there are tons of studies of how people reuse passwords, use simple passwords, and are very vulnerable to dictionary attacks.

24 hour process for what? You have to wait 24 hours to change the email? That's just plain stupid. What if the hacker got into your email as well?

The only good idea here is to validate that the email or password was changed. Unfortunately that isn't going to happen since a lot of users here just registered with a fake email address.

No. This has been discussed before. Cloudflare does not provide any additional security whatsoever, in fact, they actually reduce your security. Cloudflare acts as a man in the middle, they can see all of your communication in plaintext, not encrypted as it should be. This opens up a whole other attack vector and a bunch more problems.

The forum is already very secure; it's part of the reason that the SMF version hasn't been updated, many many changes have been made to significantly increase the security. The problem is when people fall for phishing scams, use weak passwords, or set a security question. There is only so much the forum can do to protect you from yourself.

If you are requesting a new address (as you should) for every receive, then it is possible that you will lose money. If you use Bitcoin Core 0.13.0+, then you will be fine regardless as long as you don't change (or add) a password. If you use older versions of Bitcoin Core, then after you have used 100 addresses (can be either from requesting new ones or change addresses), your old backup will be useless.

It's unlikely that is cached. I was unable to find anything in the chrome cache that had anything that bitaddress generated.

Try looking through the file history again. If it did backup wallet B before you overwrote it, you should be able to still access it.

Otherwise, the file is lost and unfortunately you won't be able to access your Bitcoin again.

DO NOT SEND your wallet.dat file unless you absolutely trust that person. Your wallet is not encrypted, so whoever you send it to could steal your Bitcoin.

Can you please repost your debug.log? The link seems to be down.

What exactly have you tried in order to recover your Bitcoin. Don't just say "everything in this thread", please list them out (some of the things said in this thread are stupid and others you do not seem to have actually done).

So you have wallet A originally. Then you overwrite that with wallet B. From wallet B you have sent and received coins. Then you overwrite wallet B with wallet A. You now need to get wallet B. Yes?

If that is the case, you have sent and received from wallet B. In order to have done that you needed to have imported it into a wallet software. What did you use to send the Bitcoin?

I don't think so. I'm pretty sure bitaddress does stuff to prevent things from being cached.

Then what does
mean?

Did you send from the address in question?

In order to have sent from that paper wallet, you need to have imported the private key into a wallet software. Do you still have that software? The private key should still be in that wallet.

Click on one of the links to download the file of the same name. Choose the one for your OS. The zip and tar files are either just the binaries or the source. If you want the installer, download one of the other files (dmg or exe).