<p>Brainwallet.org doesn't make this terribly clear: choosing a compressed versus an uncompressed address <strong>is not choosing between two different versions</strong> of the same address, but rather <strong>two different addresses</strong> based on the same secret exponent. Sending bitcoin to one address <strong>will not be accessible</strong> by the other, as they are technically independent. With that in mind, we can address your second point first:</p>

<ul>
<li><em>Will I see the coins?</em> Of course! You can see everything that happens
on the block chain.</li>
<li><em>Would I be able to spend them if I saw them sitting in the other address?</em> No. Unless you have access to the private key for the other address, you cannot spend the coins.</li>
</ul>

<p>As for the first point, it really depends on whether or not your client supports signing transactions with compressed private keys. Your client will always be able to receive coins at the public address, but it may not be able to process a compressed private key and thus not be able to spend with it.</p>

<p>Here's some info on popular clients that might be helpful:</p>

<p><em>BlockChain.info</em> --
Currently, if you try to import a compressed private key into blockchain.info's web app, you will get a warning that they key will not be usable to create transactions on the mobile app. So, if you need to make payments with their mobile app, don't use compressed private keys. Although their web app, should work fine, even if accessed from mobile.</p>

<p><em>Bitcoin (Android - Andreas Schildbach)</em>--
Andreas Schildbach Android bitcoin client, on the other hand uses compressed private keys. Although they are normally hidden from user, there is a (somewhat convoluted) way to import and export private keys into the app and out of the app. So, if you are making payments with this app, you can use compressed private keys. (Note: I'm actually unclear as to whether or not you can import uncompressed keys into this client, so compressed keys might actually be mandatory here.)</p>

<p><em>Armory</em> --
I don't believe that the Armory supports importing of private keys at this time. So, if you're planning on using this, you must use uncompressed keys.</p>

<p>As for your third point, I would suggest remembering your chosen option just in case the clients you wish to use doesn't support it compressed keys. That way, you have a good idea of what's going on in case making a transaction fails.</p>

CC BY-SA 3.0
2013-09-13T03:13:28.870Z
I know I can see them in the blockchain, I meant see them in my balance (I guess I can't). So are you sure they are different private keys? Why call them compressed/uncompressed then? If I have the uncompressed one, can't I get the compressed one and viceversa, and then spend the coins? I think armory supports importing keys, but it doesn't support recovering them from your paper backup obviously.
ChocoDeveloper
CC BY-SA 3.0
2013-09-13T11:35:56.227Z
I'm pretty sure that they are different keys, but I'd be willing to hear arguments to the contrary. If there is a normal private key, there should also be a corresponding compressed private key and they should each correspond to the same public key. However, the process that brainwallet.org uses to produce compressed verses normal keys results in two different key pairs -- rather than two different private keys with the same public key. (Note: the public does not remain the same when toggling.). I tried importing a compressed key into Armory, and it failed, perhaps I did something else wrong?
John Henry
CC BY-SA 3.0
2013-09-18T20:09:23.913Z
So, I got some down votes on this one? Anybody care to explain? I'm trying to make my answers as accurate and thorough as possible.
John Henry
CC BY-SA 3.0
2013-09-12T20:27:58.303Z
2013-09-13T11:22:59.677Z
2013-09-13T11:22:59.677Z
John Henry
<p>It makes no difference which you choose.</p>

<p>For more info please see the answer to this question: 
<a href="https://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key/3062#3062">What is a compressed Bitcoin key?</a></p>

<blockquote>
  <p>A compressed key is just a way of storing a public key in fewer bytes (33 instead of 65). There are no compatibility or security issues because they are precisely the same keys, just stored in a different way. </p>
</blockquote>

CC BY-SA 3.0
2013-09-12T19:52:43.487Z
Most clients allow the import of compressed private keys, but some clients -- particularly older versions -- and the services which use those clients may not work for compressed keys.
Stephen Gornick
CC BY-SA 3.0
2013-09-12T17:58:44.800Z
2013-09-12T17:58:44.800Z
2017-04-13T12:47:36.647Z
Skunkhomonstant
<ul>
<li>When creating a brain wallet, should I choose the compressed or uncompressed version? Why?</li>
<li>What happens if I choose the uncompressed version (which is what the official client uses, right?), and someone sends coins to the compressed address? Will I see the coins? Would I be able to spend them if I saw them sitting in the other address?</li>
<li>Will I have to remember which option I chose, or the pass phrase is enough? Will other options keep popping up? (eg: super compressed)</li>
</ul>

<private-key><brain-wallet>
Compressed or uncompressed for brainwallet?
ChocoDeveloper
# Compressed or uncompressed for brainwallet?

(Asked by: username_0 on 2013-09-12)

* When creating a brain wallet, should I choose the compressed or uncompressed version? Why?
* What happens if I choose the uncompressed version (which is what the official client uses, right?), and someone sends coins to the compressed address? Will I see the coins? Would I be able to spend them if I saw them sitting in the other address?
* Will I have to remember which option I chose, or the pass phrase is enough? Will other options keep popping up? (eg: super compressed)

**Tags:** private-key, brain-wallet


---

## 2 answers

### Answer by username_1 on 2013-09-12. Score: 2

Brainwallet.org doesn't make this terribly clear: choosing a compressed versus an uncompressed address **is not choosing between two different versions** of the same address, but rather **two different addresses** based on the same secret exponent. Sending bitcoin to one address **will not be accessible** by the other, as they are technically independent. With that in mind, we can address your second point first:

* *Will I see the coins?* Of course! You can see everything that happens
  on the block chain.
* *Would I be able to spend them if I saw them sitting in the other address?* No. Unless you have access to the private key for the other address, you cannot spend the coins.

As for the first point, it really depends on whether or not your client supports signing transactions with compressed private keys. Your client will always be able to receive coins at the public address, but it may not be able to process a compressed private key and thus not be able to spend with it.

Here's some info on popular clients that might be helpful:

*BlockChain.info* --
Currently, if you try to import a compressed private key into blockchain.info's web app, you will get a warning that they key will not be usable to create transactions on the mobile app. So, if you need to make payments with their mobile app, don't use compressed private keys. Although their web app, should work fine, even if accessed from mobile.

*Bitcoin (Android - Andreas Schildbach)*--
Andreas Schildbach Android bitcoin client, on the other hand uses compressed private keys. Although they are normally hidden from user, there is a (somewhat convoluted) way to import and export private keys into the app and out of the app. So, if you are making payments with this app, you can use compressed private keys. (Note: I'm actually unclear as to whether or not you can import uncompressed keys into this client, so compressed keys might actually be mandatory here.)

*Armory* --
I don't believe that the Armory supports importing of private keys at this time. So, if you're planning on using this, you must use uncompressed keys.

As for your third point, I would suggest remembering your chosen option just in case the clients you wish to use doesn't support it compressed keys. That way, you have a good idea of what's going on in case making a transaction fails.

> **Comments:**
> **username_0**: I know I can see them in the blockchain, I meant see them in my balance (I guess I can't). So are you sure they are different private keys? Why call them compressed/uncompressed then? If I have the uncompressed one, can't I get the compressed one and viceversa, and then spend the coins? I think armory supports importing keys, but it doesn't support recovering them from your paper backup obviously.  
> **username_1**: I'm pretty sure that they are different keys, but I'd be willing to hear arguments to the contrary. If there is a normal private key, there should also be a corresponding compressed private key and they should each correspond to the same public key. However, the process that brainwallet.org uses to produce compressed verses normal keys results in two different key pairs -- rather than two different private keys with the same public key. (Note: the public does not remain the same when toggling.). I tried importing a compressed key into Armory, and it failed, perhaps I did something else wrong?  
> **username_1**: So, I got some down votes on this one? Anybody care to explain? I'm trying to make my answers as accurate and thorough as possible.  

---

### Answer by username_2 on 2013-09-12. Score: 0

It makes no difference which you choose.

For more info please see the answer to this question:
[What is a compressed Bitcoin key?](https://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key/3062#3062)

> A compressed key is just a way of storing a public key in fewer bytes (33 instead of 65). There are no compatibility or security issues because they are precisely the same keys, just stored in a different way.

> **Comments:**
> **username_3**: Most clients allow the import of compressed private keys, but some clients -- particularly older versions -- and the services which use those clients may not work for compressed keys.  

---

