MoreBloodWine
Legendary
 Offline
Activity: 1050
Merit: 1001
|
 |
March 11, 2015, 09:27:38 PM |
|
Ok, so I got cor 0.10 running, went to dl Armory 0.93 which afaik is supposed to be 0.10 compatable.
Anyway, when I run it I get some windows version error tellin me to dl a 32 or 64 bit compatable version. So what am I doing wrong here, previous version of armory ran fine but 0.93 seems fubar'd to me.
Ty.
Do you have a 32-bit version of Windows? Due to an oversight, Armory 0.93 can't be installed on them. If using for offline-only, you'll need to roll back to 0.92.3 for now. If using for online, you'll have to wait and see if service is restored. (Despite the oversight, running online Armory on a 32-bit system really can't be done just yet anyway.) Of course it's 32 bit, anyway, hope the oversight is fixed. That being said, can I use my own rpc user / pass with armory or does it have to be those supplied when installing armory ? That being said, can I use my own rpc user / pass with armory or does it have to be those supplied when installing armory ? Still wanting clarification on this as well as to ask another question. In addition to the above question, 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. Since during Armory setup you requested to import the existing wallet. Do changes made to the wallet via RPC continue to import over ? Not sure I asked this the way it needed to be but hope it made sense, Ty. |
To be decided...
|
|
|
|
|
|
|
|
|
|
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
KS
|
|
March 12, 2015, 01:13:32 AM |
|
I'm with you, but then where would the .ini file be (and what if it were located in a path with non-ASCII characters)?
Good point, though I'm not using non-ASCII (8bits) characters - I guess they would be "extended ASCII" (16bits - nothing MS-DOS wasn't already using with codepage 437, 850 or "win-dos" 1250). The "right" way to do this is of course to store settings in the Windows registry, however the Armory devs have to support multiple OS's, and it's understandable that they don't want to have to maintain different code paths for every OS.
"Right way" is debatable  but I think the way it's actually implemented is fine. It's just it's not working as it should. Interesting. There could actually be 2 separate issues. 1/ with Armory itself and the /-slash and 2/ with Bitcoin Core itself not liking non-ASCII (8bits) characters -or it's sth else entirely (luckily workarounds exist) |
|
|
|
|
etotheipi (OP)
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
March 14, 2015, 04:42:15 AM |
|
|
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 14, 2015, 06:58:11 AM |
|
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. |
To be decided...
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
March 14, 2015, 07:18:42 AM |
|
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. |
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 14, 2015, 04:29:38 PM |
|
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. Loooooooovely. |
To be decided...
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
March 14, 2015, 09:57:10 PM |
|
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. Loooooooovely. No point building a x86 version that can't run in x86 anyways. |
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 14, 2015, 11:09:59 PM |
|
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. Loooooooovely. No point building a x86 version that can't run in x86 anyways. Everything seemed to run fine in 32bit up until the last stable version 0.93. |
To be decided...
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
March 14, 2015, 11:17:16 PM |
|
Everything seemed to run fine in 32bit up until the last stable version 0.93.
New DB engine |
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 15, 2015, 01:05:51 AM |
|
Everything seemed to run fine in 32bit up until the last stable version 0.93.
New DB engine Ahh, well here's hoping we get 32bit back. Would hate to downgrade QT to use armory on my laptop. 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 ? |
To be decided...
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
March 15, 2015, 03:45:00 AM |
|
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 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 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. |
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 15, 2015, 06:19:00 AM |
|
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 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 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. 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 ? |
To be decided...
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
March 15, 2015, 08:36:57 PM |
|
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. |
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 16, 2015, 12:01:43 AM |
|
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. 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. |
To be decided...
|
|
|
goatpig
Moderator
Legendary
Offline
Activity: 3668
Merit: 1345
Armory Developer
|
|
March 16, 2015, 01:29:50 AM
Last edit: March 16, 2015, 02:59:56 AM by goatpig |
|
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. |
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 16, 2015, 01:53:29 AM |
|
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. I know the chances of something like that being implemented is low, but where might I make an official request to try ? |
To be decided...
|
|
|
|
picobit
|
|
March 16, 2015, 08:44:25 AM |
|
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?
|
|
|
|
|
etotheipi (OP)
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
March 18, 2015, 11:52:21 PM |
|
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. |
|
|
|
mmortal03
Legendary
Offline
Activity: 1762
Merit: 1010
|
|
March 19, 2015, 12:40:13 AM |
|
The description page inside the app says the 0.93.1 release date was March 13, 2015. Should it not now say March 18th? |
|
|
|
|
MoreBloodWine
Legendary
Offline
Activity: 1050
Merit: 1001
|
|
March 19, 2015, 07:41:54 PM |
|
--- 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 ! Thx for the update etotheipi ;-) |
To be decided...
|
|
|
|
