Topic: Armory - Discussion Thread - page 10. (Read 521821 times)
Yes, something about Armory not having to build its own DB anymore, so you won't have a double blockchain on your storage medium
Is it my impression or the database is a tad smaller compared with the previous version?
I observed the same (maybe a GB or so). Won't matter once goatpig does the next stage in the Db redevelopment, he quoted something like 120 MB Db for that setup.
Just to let you know that Armory 0.93.1 is working like a charm on my OS X 10.10.2. No more db errors and superfast start up. Is it my impression or the database is a tad smaller compared with the previous version?
Good job!
Good job!
--- snip ---
NOTE: As of 0.93, we broke compatibility with both Ubuntu 12.04 (32 and 64) and Windows 32 bit. The next major release (hopefully soon) will actually remove the bulky Armory databases (except in supernode, of course), and thus make it compatible with 32-bit again.
Sounds good !NOTE: As of 0.93, we broke compatibility with both Ubuntu 12.04 (32 and 64) and Windows 32 bit. The next major release (hopefully soon) will actually remove the bulky Armory databases (except in supernode, of course), and thus make it compatible with 32-bit again.
Thx for the update etotheipi ;-)
Armory 0.93.1 -- Fixes most BDM issues and the Fragmented backup UI issues.
As usual, please use Help->Update Software within the app to use the secure downloader, if possible.
Armory 0.93.1 for Windows XP, Vista, 7, 8+ (64-bit)
Armory 0.93.1 for MacOSX 10.7+ (64bit)
Armory 0.93.1 for Ubuntu 12.04+ (32bit)
Armory 0.93.1 for Ubuntu 12.04+ (64bit)
Armory 0.93.1 for RaspberryPi (armhf)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (32bit)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (64bit)
Armory 0.93.1 Offline Bundle for RaspberryPi (armhf)
Armory 0.93.1: Signed hashes of all installers
NOTE: As of 0.93, we broke compatibility with both Ubuntu 12.04 (32 and 64) and Windows 32 bit. The next major release (hopefully soon) will actually remove the bulky Armory databases (except in supernode, of course), and thus make it compatible with 32-bit again.
As usual, please use Help->Update Software within the app to use the secure downloader, if possible.
Armory 0.93.1 for Windows XP, Vista, 7, 8+ (64-bit)
Armory 0.93.1 for MacOSX 10.7+ (64bit)
Armory 0.93.1 for Ubuntu 12.04+ (32bit)
Armory 0.93.1 for Ubuntu 12.04+ (64bit)
Armory 0.93.1 for RaspberryPi (armhf)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (32bit)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (64bit)
Armory 0.93.1 Offline Bundle for RaspberryPi (armhf)
Armory 0.93.1: Signed hashes of all installers
NOTE: As of 0.93, we broke compatibility with both Ubuntu 12.04 (32 and 64) and Windows 32 bit. The next major release (hopefully soon) will actually remove the bulky Armory databases (except in supernode, of course), and thus make it compatible with 32-bit again.
The description page inside the app says the 0.93.1 release date was March 13, 2015. Should it not now say March 18th?
Armory 0.93.1 -- Fixes most BDM issues and the Fragmented backup UI issues.
As usual, please use Help->Update Software within the app to use the secure downloader, if possible.
Armory 0.93.1 for Windows XP, Vista, 7, 8+ (64-bit)
Armory 0.93.1 for MacOSX 10.7+ (64bit)
Armory 0.93.1 for Ubuntu 12.04+ (32bit)
Armory 0.93.1 for Ubuntu 12.04+ (64bit)
Armory 0.93.1 for RaspberryPi (armhf)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (32bit)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (64bit)
Armory 0.93.1 Offline Bundle for RaspberryPi (armhf)
Armory 0.93.1: Signed hashes of all installers
NOTE: As of 0.93, we broke compatibility with both Ubuntu 12.04 (32 and 64) and Windows 32 bit. The next major release (hopefully soon) will actually remove the bulky Armory databases (except in supernode, of course), and thus make it compatible with 32-bit again.
As usual, please use Help->Update Software within the app to use the secure downloader, if possible.
Armory 0.93.1 for Windows XP, Vista, 7, 8+ (64-bit)
Armory 0.93.1 for MacOSX 10.7+ (64bit)
Armory 0.93.1 for Ubuntu 12.04+ (32bit)
Armory 0.93.1 for Ubuntu 12.04+ (64bit)
Armory 0.93.1 for RaspberryPi (armhf)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (32bit)
Armory 0.93.1 Offline Bundle for Ubuntu 12.04 exact (64bit)
Armory 0.93.1 Offline Bundle for RaspberryPi (armhf)
Armory 0.93.1: Signed hashes of all installers
NOTE: As of 0.93, we broke compatibility with both Ubuntu 12.04 (32 and 64) and Windows 32 bit. The next major release (hopefully soon) will actually remove the bulky Armory databases (except in supernode, of course), and thus make it compatible with 32-bit again.
I don't think they should implement that. The main selling point of Armory is security, both security against theft (as in using offline wallets) but more importantly security against loss of bitcoins, implemented through paper backups. If you automatically import keys you lose both: Your bitcoins are no more secure than the weakest wallet, and they do not get backed up.
What is the use-case for automatic import? Why not just use one of the wallets?
What is the use-case for automatic import? Why not just use one of the wallets?
I'm not sure what you mean by that. You will get full up-to-date transaction history for any private key you import into an Armory wallet, past, present and future. If you create new private keys in a wallet from another client, you will have to import these new keys into your Armory wallet to get their history.
What I meant was I assume to import new keys after the initial import during armory setup, that you have to manually import via a menu somewhere where as I was asking about telling armory to check for new keys from the QT client and import if found. So everything otherwise would remain automatic with new keys needing to be imported.Nothing like that sorry. All key imports are manual.
What I meant was I assume to import new keys after the initial import during armory setup, that you have to manually import via a menu somewhere where as I was asking about telling armory to check for new keys from the QT client and import if found. So everything otherwise would remain automatic with new keys needing to be imported.
Nothing like that sorry. All key imports are manual.
I'll have to read up on auto bitcoind, I've seen it referenced a few times. As for the import thing, could armory be told to "look" for changes and import at x intervals ?
I'm not sure what you mean by that. You will get full up-to-date transaction history for any private key you import into an Armory wallet, past, present and future. If you create new private keys in a wallet from another client, you will have to import these new keys into your Armory wallet to get their history.
I'll have to read up on auto bitcoind, I've seen it referenced a few times. As for the import thing, could armory be told to "look" for changes and import at x intervals ?
I'm not sure what you mean by that. You will get full up-to-date transaction history for any private key you import into an Armory wallet, past, present and future. If you create new private keys in a wallet from another client, you will have to import these new keys into your Armory wallet to get their history.
Ahh, well here's hoping we get 32bit back. Would hate to downgrade QT to use armory on my laptop.
We said we'll deliver next version
Quote
1) Can I use my own rpc user / pass with armory or does it have to be those supplied when installing armory ?
Not if you use auto bitcoind. With BitcoinQt you can set your own RPC password
Quote
2) If when setting up armory, you import an existing wallet from the QT client. If something RPC's in to the node and modifies the wallet by making new ones with labels etc. Since during Armory setup you requested to import the existing wallet. Do changes made to the wallet via RPC continue to import over ?
No, Armory and Core wallets are completely different. You can't import Core wallets into Armory as is, you have to import the private keys, which will become part of the Armory wallet. New private keys created in the Core wallet will be unknown to Armory until you import these too.
Ahh, well here's hoping we get 32bit back. Would hate to downgrade QT to use armory on my laptop.
We said we'll deliver next version
Quote
1) Can I use my own rpc user / pass with armory or does it have to be those supplied when installing armory ?
Not if you use auto bitcoind. With BitcoinQt you can set your own RPC password
Quote
2) If when setting up armory, you import an existing wallet from the QT client. If something RPC's in to the node and modifies the wallet by making new ones with labels etc. Since during Armory setup you requested to import the existing wallet. Do changes made to the wallet via RPC continue to import over ?
No, Armory and Core wallets are completely different. You can't import Core wallets into Armory as is, you have to import the private keys, which will become part of the Armory wallet. New private keys created in the Core wallet will be unknown to Armory until you import these too.
Everything seemed to run fine in 32bit up until the last stable version 0.93.
New DB engine
On that note, think you could shed light on any of these question to which I thank you in advance.
1) Can I use my own rpc user / pass with armory or does it have to be those supplied when installing armory ?
2) If when setting up armory, you import an existing wallet from the QT client. If something RPC's in to the node and modifies the wallet by making new ones with labels etc. Since during Armory setup you requested to import the existing wallet. Do changes made to the wallet via RPC continue to import over ?
Everything seemed to run fine in 32bit up until the last stable version 0.93.
New DB engine
so aside from my previous reply I'm still waiting for a reply on, will the next version actually include Windows 32 bit? I ask because it seems you're latest reply suggests that we're still focusing on 64 bit for Windows.
No, this version is just for bug fixes, you'll have to wait for the version with DB changes.
No point building a x86 version that can't run in x86 anyways.
so aside from my previous reply I'm still waiting for a reply on, will the next version actually include Windows 32 bit? I ask because it seems you're latest reply suggests that we're still focusing on 64 bit for Windows.
No, this version is just for bug fixes, you'll have to wait for the version with DB changes.
No point building a x86 version that can't run in x86 anyways.
so aside from my previous reply I'm still waiting for a reply on, will the next version actually include Windows 32 bit? I ask because it seems you're latest reply suggests that we're still focusing on 64 bit for Windows.
No, this version is just for bug fixes, you'll have to wait for the version with DB changes.
so aside from my previous reply I'm still waiting for a reply on, will the next version actually include Windows 32 bit? I ask because it seems you're latest reply suggests that we're still focusing on 64 bit for Windows.
No, this version is just for bug fixes, you'll have to wait for the version with DB changes.
It's been a bumpy road, but I think we're finally getting there...
So we had a problem with auto-manage bitcoind in the .80 testing release (it's a pain to test with auto-bitcoind, so we miss that easily). Sorry! Hopefully this is the last testing release before the 0.93.1!
As usual, use the secure downloader to get it. Only use the links below as a backup:
Armory 0.93.0.82-testing for Windows XP, Vista, 7, 8+ (64-bit)
Armory 0.93.0.82-testing for MacOSX 10.7+ (64bit)
Armory 0.93.0.82-testing for Ubuntu 12.04+ (32bit)
Armory 0.93.0.82-testing for Ubuntu 12.04+ (64bit)
Armory 0.93.0.82-testing for RaspberryPi (armhf)
Armory 0.93.0.82-testing Offline Bundle for Ubuntu 12.04 exact (32bit)
Armory 0.93.0.82-testing Offline Bundle for Ubuntu 12.04 exact (64bit)
Armory 0.93.0.82-testing Offline Bundle for RaspberryPi (armhf)
Armory 0.93.0.82-testing: Signed hashes of all installers
so aside from my previous reply I'm still waiting for a reply on, will the next version actually include Windows 32 bit? I ask because it seems you're latest reply suggests that we're still focusing on 64 bit for Windows. So we had a problem with auto-manage bitcoind in the .80 testing release (it's a pain to test with auto-bitcoind, so we miss that easily). Sorry! Hopefully this is the last testing release before the 0.93.1!
As usual, use the secure downloader to get it. Only use the links below as a backup:
Armory 0.93.0.82-testing for Windows XP, Vista, 7, 8+ (64-bit)
Armory 0.93.0.82-testing for MacOSX 10.7+ (64bit)
Armory 0.93.0.82-testing for Ubuntu 12.04+ (32bit)
Armory 0.93.0.82-testing for Ubuntu 12.04+ (64bit)
Armory 0.93.0.82-testing for RaspberryPi (armhf)
Armory 0.93.0.82-testing Offline Bundle for Ubuntu 12.04 exact (32bit)
Armory 0.93.0.82-testing Offline Bundle for Ubuntu 12.04 exact (64bit)
Armory 0.93.0.82-testing Offline Bundle for RaspberryPi (armhf)
Armory 0.93.0.82-testing: Signed hashes of all installers
Jump to: