just downloaded 0.9 and works great!
question; i've been opening Bitcoin-qt separately then opening 0.9 which obviously is scanning blockchain much faster. how is it performing if i let Armory control Bitcoin-qt?
Topic: Armory - Discussion Thread - page 85. (Read 521763 times)
Hi I'm using Armory for the first time. I created a wallet on my offline computer. When I open Armory on my online computer, it just sits there saying Offline. How do I turn it online?
Yes I downloaded QT and fully downloaded the blockchain, fully updating it.
Thanks,
Yes I downloaded QT and fully downloaded the blockchain, fully updating it.
Thanks,
My request would be to update the fees logic to what's being implemented in Qt/d 0.8.6. It's in release candidate stage right now, but I expect it will be fully released before 0.91.
I didn't realize it was changing again. What will it be now?
We just updated the logic in 0.90 to use 0.0001 BTC as the base.
It's more subtle than the per-kilobyte when less than 0.01 BTC rate, here's a link to the details: https://gist.github.com/gavinandresen/7670433#086-wallet
Not sure if the relaying change is relevant to Armory, the network will handle that according to majority version of the main client.
i have had it for 4-5 days and have started it up at least 6 times. Every time it takes 20 minutes.
Should I re-download?
Should I re-download?
Are you closing Armory "properly"? It will rescan every time there's an unclean shutdown, to avoid any SNAFU-problems associated with close-but-not-actually-correct wallet histories. If you shutdown Armory using "File"->"Quit Armory" or use the (X) in the corner, it should be fine. If you're rebooting without closing Armory first, or you're killing it through the task manager, you'll be rescanning every time.
In 0.91-beta I'll experiment with removing clean-shutdown criteria. I know it's annoying, but I determined the risk of people with seemingly-correct histories that aren't actually correct could cause serious problems (invisible coins, lost coins and/or inability to send).
That's probably it. I close my PC but don't turn it off when I'm in transit. Sometimes when I open it back up Armory will crash. Sometimes not. I bet that's the reason. Thanks!
My request would be to update the fees logic to what's being implemented in Qt/d 0.8.6. It's in release candidate stage right now, but I expect it will be fully released before 0.91.
I didn't realize it was changing again. What will it be now?
We just updated the logic in 0.90 to use 0.0001 BTC as the base.
Here https://gist.github.com/gavinandresen/7670433#086-relaying
My request would be to update the fees logic to what's being implemented in Qt/d 0.8.6. It's in release candidate stage right now, but I expect it will be fully released before 0.91.
I didn't realize it was changing again. What will it be now?
We just updated the logic in 0.90 to use 0.0001 BTC as the base.
My request would be to update the fees logic to what's being implemented in Qt/d 0.8.6. It's in release candidate stage right now, but I expect it will be fully released before 0.91.
i have had it for 4-5 days and have started it up at least 6 times. Every time it takes 20 minutes.
Should I re-download?
Should I re-download?
Are you closing Armory "properly"? It will rescan every time there's an unclean shutdown, to avoid any SNAFU-problems associated with close-but-not-actually-correct wallet histories. If you shutdown Armory using "File"->"Quit Armory" or use the (X) in the corner, it should be fine. If you're rebooting without closing Armory first, or you're killing it through the task manager, you'll be rescanning every time.
In 0.91-beta I'll experiment with removing clean-shutdown criteria. I know it's annoying, but I determined the risk of people with seemingly-correct histories that aren't actually correct could cause serious problems (invisible coins, lost coins and/or inability to send).
i have had it for 4-5 days and have started it up at least 6 times. Every time it takes 20 minutes.
Should I re-download?
Should I re-download?
So I downloaded the .91 beta. But it's back to taking forever to start up. Literally 20 minutes.
Is it suppose to do that. I thought the last version fixed that.
Is it suppose to do that. I thought the last version fixed that.
The first time you run the new version, it has to read the block data from bitcoin's data directory and write its own to the armory data directory. This takes a while, but only has to be done once. Subsequent startups will read the block data from the armory directory much more quickly.
So I downloaded the .91 beta. But it's back to taking forever to start up. Literally 20 minutes.
Is it suppose to do that. I thought the last version fixed that.
Is it suppose to do that. I thought the last version fixed that.
Hello etotheipi and all Armory users!
We've made a review of Armory wallet: bitcoinsites.org/bitcoinarmory/
We've made a review of Armory wallet: bitcoinsites.org/bitcoinarmory/
Another small request please.
Can you add the printable special characters to the mouse keyboard for wallet password. A few are there, but most missing. Thanks!
Can you add the printable special characters to the mouse keyboard for wallet password. A few are there, but most missing. Thanks!
That's one of the little things going into 0.91-beta ... added support for all character encodings/types, except inside wallets (which the wallet format and code was not designed to accommodate). When I finally finish the new wallet format, then we can can have a fully internationalized app, with no restrictions anywhere. Then we can also start prepping the app for localization & translations.
It's coming...
Another small request please.
Can you add the printable special characters to the mouse keyboard for wallet password. A few are there, but most missing. Thanks!
Can you add the printable special characters to the mouse keyboard for wallet password. A few are there, but most missing. Thanks!
Small request, or maybe it has already been implemented somehow. Can Armory users get the option to switch into mBTC please?
Not yet. But we'll be adding it to 0.91-beta. That version is mostly bug-fixes, usability upgrades, polishing, etc. Things like sending to P2SH, unicode fixes, alternate units, will all be implemented then.
Small request, or maybe it has already been implemented somehow. Can Armory users get the option to switch into mBTC please?
That went straight over my head (I'm coding-challenged) 
. Anyhow, does this mean that I have to create a new set of paper and digital backups of all my wallets/private keys on the offline machine after upgrading? It's probably not likely but I just want to be sure.
. Anyhow, does this mean that I have to create a new set of paper and digital backups of all my wallets/private keys on the offline machine after upgrading? It's probably not likely but I just want to be sure.You don't have to unless you want to use the feature. If you're fine with single sheet paper backups, there's no need to move to M-of-N. The later isn't replacing the former, it's an added feature.
OK. Got it! Thanks again.
That went straight over my head (I'm coding-challenged) . Anyhow, does this mean that I have to create a new set of paper and digital backups of all my wallets/private keys on the offline machine after upgrading? It's probably not likely but I just want to be sure.
. Anyhow, does this mean that I have to create a new set of paper and digital backups of all my wallets/private keys on the offline machine after upgrading? It's probably not likely but I just want to be sure.You don't have to unless you want to use the feature. If you're fine with single sheet paper backups, there's no need to move to M-of-N. The later isn't replacing the former, it's an added feature.
Thanks for the quick reply, goatpig. I might as well go all the way and upgrade both. What's an M-of-N feature BTW? I haven't seen that term/acronym on the website.
One of the new backup feature: constructs a wallet backup made of N fragments, which can be a mix of paper and digital backups. Requires M (M<=N) fragments to recompose the wallet. Currently M spans from 2 to 8 and N from 2 to 12.
That went straight over my head (I'm coding-challenged)
. Anyhow, does this mean that I have to create a new set of paper and digital backups of all my wallets/private keys on the offline machine after upgrading? It's probably not likely but I just want to be sure. Thanks for the quick reply, goatpig. I might as well go all the way and upgrade both. What's an M-of-N feature BTW? I haven't seen that term/acronym on the website.
One of the new backup feature: constructs a wallet backup made of N fragments, which can be a mix of paper and digital backups. Requires M (M<=N) fragments to recompose the wallet. Currently M spans from 2 to 8 and N from 2 to 12.
Jump to: