Pages:
Author

Topic: Does Armory use compressed keys? (Read 8954 times)

newbie
Activity: 12
Merit: 0
February 01, 2018, 03:29:48 PM
#35
wow necro... go through the changelogs.

I tried today again to import a compressed private key, but same error. After your last reply i thought something must have changed, but after i gone through the changelogs again, i found nothing new?!? So the answer to my question

Nothing new?

Could be "not yet." or did i miss something?
Its on your to-do-list, right?
newbie
Activity: 12
Merit: 0
December 25, 2017, 08:19:58 PM
#34
ahh ok.. just tried to import an private key (export with bitcoin-core-0.15.1) in Armory-0.96.399.

but https://picload.org/view/dddgggga/apk.png.html

Googled and found this Thread..
legendary
Activity: 3766
Merit: 1364
Armory Developer
December 25, 2017, 02:01:52 PM
#33
wow necro... go through the changelogs.
newbie
Activity: 12
Merit: 0
December 25, 2017, 06:28:04 AM
#32
Nothing new?
legendary
Activity: 1022
Merit: 1004
August 30, 2015, 04:46:46 PM
#31
Thanks for clearing this up.
Too bad.. Sad
legendary
Activity: 3430
Merit: 3080
August 30, 2015, 10:35:41 AM
#30
I just bumped into this old thread when I tried to import a (compressed, for sure) privkey
from multibit to armory. Is it really possible that armory *still* does not support importing
compressed private keys? Huh

New wallet format is not yet available in Armory, so sadly not. Nope, no idea when.
legendary
Activity: 1022
Merit: 1004
August 30, 2015, 05:42:54 AM
#29
I just bumped into this old thread when I tried to import a (compressed, for sure) privkey
from multibit to armory. Is it really possible that armory *still* does not support importing
compressed private keys? Huh
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
October 20, 2014, 11:23:00 AM
#28
As mentioned above, the new wallet format is coming soon and Armory will finally understand compressed keys and know what to do with them.

That's good to know. I check in here occasionally to see what're the latest developments. Thanks for the good work you put into this!
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
August 10, 2014, 06:12:22 PM
#27
I want to import some private keys from the Bitcoin-Qt. I used the dumpprivkey command to get the keys, but it seems like it can't be imported to Armory because these are compressed keys.

Is there any way to dump non-compresses keys from Qt so that I can use the same addresses on Armory?

Unfortunately not.  Compressed and uncompressed keys have different addresses.  Even if you get the uncompressed version from Bitcoin Core and import it into Armory, it will show a different address and no balance. 

As mentioned above, the new wallet format is coming soon and Armory will finally understand compressed keys and know what to do with them.
legendary
Activity: 812
Merit: 1002
August 10, 2014, 03:41:27 PM
#26
I want to import some private keys from the Bitcoin-Qt. I used the dumpprivkey command to get the keys, but it seems like it can't be imported to Armory because these are compressed keys.

Is there any way to dump non-compresses keys from Qt so that I can use the same addresses on Armory?
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
August 09, 2014, 07:07:43 PM
#25
Updates? Also, since MS quit on XP, does that mean you (or Goat Pig) will stop making it work for XP?

(Believe it or not, I still use XP today.)

XP? *shudders*
:-P

Compressed keys will be supported with the new (BIP0032 compatible) wallet format.
That is one of the next bigger projects, so it'll be here eventually. As I understand it.

Ente

Yes. I usually use the previous 2 or 3 generations of older software while they still work on the latest hardware (or because I tend to get old hardware for free or very cheap.)

Good to know that compressed keys will be supported. I think it's way overdue.
legendary
Activity: 2126
Merit: 1001
August 09, 2014, 01:23:45 PM
#24
Updates? Also, since MS quit on XP, does that mean you (or Goat Pig) will stop making it work for XP?

(Believe it or not, I still use XP today.)

XP? *shudders*
:-P

Compressed keys will be supported with the new (BIP0032 compatible) wallet format.
That is one of the next bigger projects, so it'll be here eventually. As I understand it.

Ente
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
August 08, 2014, 09:41:16 AM
#23
Updates? Also, since MS quit on XP, does that mean you (or Goat Pig) will stop making it work for XP?

(Believe it or not, I still use XP today.)
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
June 08, 2014, 08:52:02 AM
#22
So what's the status on Armory supporting compressed public keys?

I have a "compressed private key" that I'd really like to sweep into my Armory wallet.

We're trying hard to get these multi-sig features ironed out, tested, etc.  Once we do that, I'll finish the new wallets, which are like 80% done already.  Then there will be proper compressed key support.

legendary
Activity: 980
Merit: 1008
June 08, 2014, 02:39:05 AM
#21
So what's the status on Armory supporting compressed public keys?

I have a "compressed private key" that I'd really like to sweep into my Armory wallet.
legendary
Activity: 2126
Merit: 1001
September 18, 2013, 10:37:38 AM
#20
As long as all programs recognize both compressed and uncompressed adresses, it's all good.
If, for some reason, a firstbits service only looks through the compressed or uncompressed adresses […]

Ok now I'm sure you're serious Smiley. A firstbits service doesn't need to look at this, it looks at the address and nothing else. Two different addresses can't map to the same fb, period.


I'm serious, but I'm wrong ;-)
Yes, thinking about it, what's in the blockchain is safe. Or something.

So, when eventually all programs know both formats, and may even watch both formats for a given privkey, all is fine.

Ente
legendary
Activity: 1974
Merit: 1029
September 18, 2013, 10:23:09 AM
#19
As long as all programs recognize both compressed and uncompressed adresses, it's all good.
If, for some reason, a firstbits service only looks through the compressed or uncompressed adresses […]

Ok now I'm sure you're serious Smiley. A firstbits service doesn't need to look at this, it looks at the address and nothing else. Two different addresses can't map to the same fb, period.
legendary
Activity: 2126
Merit: 1001
September 18, 2013, 09:44:27 AM
#18
Then we have compressed and uncompressed firstbits.

Not sure if serious. firstbits is a mapping to an address, whether it comes from a compressed key or not. My 12345 happens to be an uncompressed one—another address that starts with 12345 and comes from a compressed key will have different firstbits due to the need to disambiguate the prefix, not because of the underlying key.

As long as all programs recognize both compressed and uncompressed adresses, it's all good.
If, for some reason, a firstbits service only looks through the compressed or uncompressed adresses, or converts all of them to compressed or uncompressed adresses, people are mapping different adresses to the same firstbits.
This probably won't happen.
But then, I tried to import a compressed adress in Armory, didn't work. So I converted it to uncompressed, Armory importet that. But didn't show the balance after rescanning the blockchain..

I now expect unexpected behavior at every corner. Importing/exporting between clients? Blockexplorer? Firstbits? Try to explain that sht to a non-techie..

Ente
legendary
Activity: 3416
Merit: 1912
The Concierge of Crypto
September 18, 2013, 07:41:29 AM
#17
Well, firstbits is not really part of the bitcoin protocol. It's just, what are the first parts of your bitcoin address, which is first-come-first-serve in the blockchain or when your address first appears.

Don't give the firstbigs address UNTIL you have seen your FULL address being used.

I use compressed keys almost exclusively now. No reason for me to use any uncompressed keys, except old addresses that are still getting coins sent to them.
legendary
Activity: 1974
Merit: 1029
September 18, 2013, 06:29:22 AM
#16
Then we have compressed and uncompressed firstbits.

Not sure if serious. firstbits is a mapping to an address, whether it comes from a compressed key or not. My 12345 happens to be an uncompressed one—another address that starts with 12345 and comes from a compressed key will have different firstbits due to the need to disambiguate the prefix, not because of the underlying key.
Pages:
Jump to: