Please take a look and give me feedback. I'm wondering if this is what people are looking for. Also, wondering if the usability is good.

Each Private Key could have a few different BIP38 keys. This is because there is more than one way to generate a BIP38 key.

Here is an example. The Paper Wallet tab would generate an "EC Multiply" BIP38 key like #1 below. It's uncompressed and uses an intermediate point derived from the passphrase then mixed with random data to make the encrypted key.Passphrase: TestingOneTwoThree1) EC Multiply, no compression, 6PfQu77ygVyJLZjfvMLyhLMQbYnu5uguoJJ4kMCLqWwPEdfpwANVS76gTX 5K4caxezwjGCGfnoPTZ8tMcJBLB7Jvyjv4xxeacadhq8nLisLR2

If I take the WIF key above ('5xxx') then I use it on the Wallet Details tab using the passphrase above I get this BIP38 key that does NOT use "EC Multiply".2) no EC Multiply, no compression, 6PRNpUxL88gG5GeAGqQnEpTzLfzCNaq91m8TmMwMsAqWrfG9SA4CiMsCBJ 5K4caxezwjGCGfnoPTZ8tMcJBLB7Jvyjv4xxeacadhq8nLisLR2

If you take the compressed WIF key and use it on the Wallet Details tab using the passphrase above you'll get yet another BIP38 key because this key will keep track of the compression flag so you can generate the Bitcoin Address for the compressed public key.3) no EC Multiply, compression, 6PYMHFJQL84b73nEHQcfQYzGbvnPGufT4VkxC9aHr2gWJBkvpnQZtJrrMk L2ix4teikZY4kAD9k8Cqofxnpbdcr9FSREVzcsN3T1DTLkDhHDkk

To keep things simple for users I just show one key. When decrypting a BIP38 key then I just show that key. When encrypting you get the uncompressed no EC multiply BIP38 key. Unless you use the compressed WIF key then you get the compressed no EC multiply BIP38 key. I considered that these details are not important for end users. Hence, why I just show one of these versions at any given time because you can always get the same private key out anyways.

Just a sugesiton: For intermediate user everything is clear. If you are a beginner or just started playing around with key generation and bip38 stuff, I guess you would get lost in "Details tab". Maybe separate tab with a little bit of explanation would help a lot.

Quick question, does anyone know if Blockchain.info store the private key from a watch only address once you use on their site to authorize a payment? i used the private key created on Bitaddress the other day to do such a thing.

I don't know, but you should assume that they (or your own computer) store it and will one day leak it to a hacker.

To assume anything else is dangerous. You're presumably using bitaddress.org for offline storage. Once you've entered a private key online, consider it compromised, and move any remaining funds to a new address.

I'm trying to understand the use case/purpose for having the compressed address. Can anyone enlighten?

Compressed public keys are 66 hex characters. Uncompressed are 130 hex characters. Using compressed keys saves space in the block chain because the transaction size is smaller and potentially would reduce the transaction fee which is calculated by transaction size in the reference bitcoin implementation.

I'm trying to understand the use case/purpose for having the compressed address. Can anyone enlighten?

Compressed public keys are 66 hex characters. Uncompressed are 130 hex characters. Using compressed keys saves space in the block chain because the transaction size is smaller and potentially would reduce the transaction fee which is calculated by transaction size in the reference bitcoin implementation.

Also - if usage of compressed keys is preferred, it would make sense (at least to me) that compressed bitcoin address would be the first choice (on the left side) in "Wallet Details" tab.

Just my 0.00000002

Yes, I see what you are saying. I want to make wallet details less confusing. And de-emphasize the uncompressed info.

Also in v3.2.0 I found another confusing inconsistency:

If I use the 'paper wallet' or 'bulk wallet' tabs to encrypt a private key, I get a "6Pn" (compressed) or "6Pf" (not compressed) encrypted private key, whereas if I use the 'wallet details' tab to encrypt the same private key, I get a "6PY" (compressed) or "6PR" (not compressed) encrypted private key.

The little research I did tells me that 6Pn and 6Pf represent "Encryption when EC multiply mode is used" whereas 6PY and 6PR represent "Encryption when EC multiply flag is not used".

Why is "multiply mode" used in 2 of the 3 tabs offering encryption but not in the 3rd? Is that deliberate? Is there a good reason for it? Is using "multiply mode" any more or less secure than not using it?

Why are someone is going to encrypt the paper wallet? I think the bigger risk is not that the wallet get stolen instead of forget the passphrase. Or I don´t unterstand the idea behind it?

When securing your coins you have two conflicting issues to address:

1) you want to be able to access the coins at some point in the future2) you don't want anyone else to be able to access the coins without your permission

If you don't encrypt your paper wallet then you are making (1) more likely, but (2) less likely. If anyone finds your printed paper wallet they can immediately just take your coins.

So you encrypt it. It's relatively hard to crack the password on paper wallets, but there's a risk that you will forget the password yourself. So (1) is less likely, but (2) is more likely.

It's a trade off. Encrypt if you like. Or don't.

Thank you very much for your explanation. I personally think the higher risk is to forget in a couple of years the passphrase - all BTC are useless, that will be one of the hardest pain, especially if it >10k/btc