Armory is not responding.
It was working great until I added another receive address to the Armory Wallet 2 days ago.
Now it takes forever to synchronize, then locks up while showing "Armory is Online" and the bottom right showing "Connected (False blocks)".
Then ultimately showing the popup message: "ArmoryQT.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." Close program is the only option
Topic: Armory - Discussion Thread - page 65. (Read 521855 times)
Sweet! That's very encouraging, considering it wasn't compiled on a pi. It will be really easy to add it to my regular release scripts now.
When you say you had to install those things, it occurred to me I think I forgot to post the RPi dependencies. I had some issues with those three packages, and would love to know if I resolved them. But I guess I didn't bundle them with it...
If it's easy, can you wipe the pi and try it again with just the packages in the following tar.gz?
https://s3.amazonaws.com/bitcoinarmory-releases/armory_rpi_dependencies_armhf.tar.gz
When you say you had to install those things, it occurred to me I think I forgot to post the RPi dependencies. I had some issues with those three packages, and would love to know if I resolved them. But I guess I didn't bundle them with it...
If it's easy, can you wipe the pi and try it again with just the packages in the following tar.gz?
https://s3.amazonaws.com/bitcoinarmory-releases/armory_rpi_dependencies_armhf.tar.gz
When I say I installed them what I mean is I installed them as system packages:
apt-get install python-psutil python-qt4 python-twisted
Not a big deal to linux users and it keeps things clean on your end. However, I can try your new archive.
EDIT:
I tried your packages. There is a problem with the python-twisted debs you provided. Most of them are 12.3, however python-twisted-runner and python-twisted-bin were 12.0 version, which caused broken dependencies. The version in the raspian repo is 12.0, so when I removed the python-twisted and grabbed the 12.0, everything worked. BTW, the python-twisted meta package installs the following debs:
python-pam_0.4.2-13_armhf.deb
python-serial_2.5-2.1_all.deb
python-twisted-core_12.0.0-1_all.deb
python-twisted-web_12.0.0-1_all.deb
python-twisted-lore_12.0.0-1_all.deb
python-twisted-mail_12.0.0-1_all.deb
python-twisted-names_12.0.0-1_all.deb
python-twisted-news_12.0.0-1_all.deb
python-twisted-runner_12.0.0-1_all.deb
python-twisted-words_12.0.0-1_all.deb
python-twisted-conch_1:12.0.0-1_all.deb
python-twisted_12.0.0-1_all.deb
By the way, I am not posting the next testing version for a couple days, but it would be stellar if someone with a fresh Raspberry Pi could test the Raspbian build I posted a couple weeks ago. I don't need a full report on functionality, etc... just want to know if I got the dependencies right and if it runs at all on a fresh Raspbian install. I'm not very confident that it will, but I'm ready to be surprised!
https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz
https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz
Armory launched on my raspberry pi with default raspbian (2014-01-07-wheezy-raspbian). I only needed to install the following packages:
python-psutil
python-qt4
python-twisted
Things I did:
1. Launch!
2. Create new wallet
3. click around the app
Sweet! That's very encouraging, considering it wasn't compiled on a pi. It will be really easy to add it to my regular release scripts now.
When you say you had to install those things, it occurred to me I think I forgot to post the RPi dependencies. I had some issues with those three packages, and would love to know if I resolved them. But I guess I didn't bundle them with it...
If it's easy, can you wipe the pi and try it again with just the packages in the following tar.gz?
https://s3.amazonaws.com/bitcoinarmory-releases/armory_rpi_dependencies_armhf.tar.gz
By the way, I am not posting the next testing version for a couple days, but it would be stellar if someone with a fresh Raspberry Pi could test the Raspbian build I posted a couple weeks ago. I don't need a full report on functionality, etc... just want to know if I got the dependencies right and if it runs at all on a fresh Raspbian install. I'm not very confident that it will, but I'm ready to be surprised!
https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz
https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz
Armory launched on my raspberry pi with default raspbian (2014-01-07-wheezy-raspbian). I only needed to install the following packages:
python-psutil
python-qt4
python-twisted
Things I did:
1. Launch!
2. Create new wallet
3. click around the app
Why don't you update the site?
Always annoying to see developers refuse to disclose changes into their changelog. . .
https://bitcoinarmory.com/download/changelog-versions/
https://bitcoinarmory.com/download/updates-latest-commits/
Always annoying to see developers refuse to disclose changes into their changelog. . .
https://bitcoinarmory.com/download/changelog-versions/
https://bitcoinarmory.com/download/updates-latest-commits/
Is the Armory team intetested in feedback of total noobs or is it the target audience more the advanced users?
We are interested in the feedback, though we are already aware that there is a large learning curve, and barrier to entry for the app. We are working on ironing out the current state to make sure it is the best thing out there for the power-users, and now that we have a real team, we can devote resources to making an easier-to-user version.
With that in mind, feel free to provide feedback. Just don't be surprised when I inundate you with a list of things already in the woodwork to address most of it
I apologize if this is answered elsewhere but my Google powers failed me today apparently. I'm curious how, in a watch-only scenario where there is an offline client running used to sign transactions, the watch-only version of Armory generates new addresses when you select "receive bitcoin" for a new address? Aren't the public keys derived from the private keys? How are the public keys able to be generated if (as I understand it) all of the signing / encryption happens on the offline machine?
Search for "Type 2 deterministic wallets". You'll find it
I apologize if this is answered elsewhere but my Google powers failed me today apparently. I'm curious how, in a watch-only scenario where there is an offline client running used to sign transactions, the watch-only version of Armory generates new addresses when you select "receive bitcoin" for a new address? Aren't the public keys derived from the private keys? How are the public keys able to be generated if (as I understand it) all of the signing / encryption happens on the offline machine?
Is the Armory team intetested in feedback of total noobs or is it the target audience more the advanced users?
By the way, I am not posting the next testing version for a couple days, but it would be stellar if someone with a fresh Raspberry Pi could test the Raspbian build I posted a couple weeks ago. I don't need a full report on functionality, etc... just want to know if I got the dependencies right and if it runs at all on a fresh Raspbian install. I'm not very confident that it will, but I'm ready to be surprised!
https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz
https://s3.amazonaws.com/bitcoinarmory-releases/armory_0.90.99-testing_rpibuild.tar.gz
What does it say in the log file?
Cannot get Armory to sync, any tips? It Freezes at 99% and has set there for days
I've tried every solution I can find so far:
-Rescan Database
-Rebuild and Rescan Database
-Ensured my PC time was synced with time.windows.com
So far nothing ive been doing has worked, the database refuses to finish.
Any ideas? I'm locked out of my wallet!
http://pastebin.com/jaHwF8tQ
heres some of the bottom of the log file, its quite large though
I've tried every solution I can find so far:
-Rescan Database
-Rebuild and Rescan Database
-Ensured my PC time was synced with time.windows.com
So far nothing ive been doing has worked, the database refuses to finish.
Any ideas? I'm locked out of my wallet!
http://pastebin.com/jaHwF8tQ
heres some of the bottom of the log file, its quite large though
Although I wouldn't normally recommend this, I think it's no so bad to do that as long as it's your online computer with watching-only wallets. Anything stupid that the online computer does will be caught by the offline computer (as long as you actually check all the transaction details before continuing).
Of course, I may be neglecting some corner case situation, so I still wouldn't put an official endorsement behind it. But having a stable version that does the reviewing and signing certainly reduces the risk considerably. (but definitely don't use it for your offline computer yet, unless it's tiny amounts of money)
Yeah, I think I still use 0.88 on the offline computer because the risk/reward of updating the offline machine isn't favorable.Of course, I may be neglecting some corner case situation, so I still wouldn't put an official endorsement behind it. But having a stable version that does the reviewing and signing certainly reduces the risk considerably. (but definitely don't use it for your offline computer yet, unless it's tiny amounts of money)
I thought maybe I should add a "don't try this at home" disclaimer to my other post, but on the other hand I think anyone capable of using git can make their own risk analysis.
Thanks for the positive feedback! Understandably, most people post and communicate with us when things don't work, and it's not a high priority to contact us when it does work. It makes me feel like it doesn't work for anyone, even though it obviously does -- we had more than 20k downloads last month...and less than 20,000 nasty emails So, it feels good to hear a success story occasionally.
The 0.91-dev branch on GitHub works for me well enough that I use it as my primary wallet. So, it feels good to hear a success story occasionally.Although I wouldn't normally recommend this, I think it's no so bad to do that as long as it's your online computer with watching-only wallets. Anything stupid that the online computer does will be caught by the offline computer (as long as you actually check all the transaction details before continuing).
Of course, I may be neglecting some corner case situation, so I still wouldn't put an official endorsement behind it. But having a stable version that does the reviewing and signing certainly reduces the risk considerably. (but definitely don't use it for your offline computer yet, unless it's tiny amounts of money)
Thanks for the positive feedback! Understandably, most people post and communicate with us when things don't work, and it's not a high priority to contact us when it does work. It makes me feel like it doesn't work for anyone, even though it obviously does -- we had more than 20k downloads last month...and less than 20,000 nasty emails So, it feels good to hear a success story occasionally.
The 0.91-dev branch on GitHub works for me well enough that I use it as my primary wallet. So, it feels good to hear a success story occasionally.Thanks for the positive feedback! Understandably, most people post and communicate with us when things don't work, and it's not a high priority to contact us when it does work. It makes me feel like it doesn't work for anyone, even though it obviously does -- we had more than 20k downloads last month...and less than 20,000 nasty emails So, it feels good to hear a success story occasionally.
You're welcome, and please consider this an implicit plea not to discontinue the offline bundle for Ubuntu 10.04. So, it feels good to hear a success story occasionally.etothepi and team, thanks for creating such an awesome and secure client!
My installation might actually be a bit below memory specifications, and may run slower than others', but it does work. The online machine has 4GB RAM, running 32-bit Linux (Fedora 20, upgraded using fedup from 17 -> 18 -> 19 -> 20). My two redundant offline machines, which are identical, are 455MHz Pentium III boxes with 256MB RAM, running Ubuntu 10.04 LTS and the Armory offline bundle. (I tried to install Ubuntu 12.04.3 on the offline boxes, without success. I installed Ubuntu from CD, and one of the machines apparently has a defective CD-ROM drive, resulting in a 40-hour install that ultimately succeeded -- luckily, there were no blackouts during those 40 hours, and the cats didn't unplug the machine ... 8^)
When I instantiated the second offline machine, I used only the paper wallet backup from the first offline machine to recover my wallet, and (of course) it worked like a champ. That was my own exercise in making sure this stuff really does work -- and it does!
My installation might actually be a bit below memory specifications, and may run slower than others', but it does work. The online machine has 4GB RAM, running 32-bit Linux (Fedora 20, upgraded using fedup from 17 -> 18 -> 19 -> 20). My two redundant offline machines, which are identical, are 455MHz Pentium III boxes with 256MB RAM, running Ubuntu 10.04 LTS and the Armory offline bundle. (I tried to install Ubuntu 12.04.3 on the offline boxes, without success. I installed Ubuntu from CD, and one of the machines apparently has a defective CD-ROM drive, resulting in a 40-hour install that ultimately succeeded -- luckily, there were no blackouts during those 40 hours, and the cats didn't unplug the machine ... 8^)
When I instantiated the second offline machine, I used only the paper wallet backup from the first offline machine to recover my wallet, and (of course) it worked like a champ. That was my own exercise in making sure this stuff really does work -- and it does!
Thanks for the positive feedback! Understandably, most people post and communicate with us when things don't work, and it's not a high priority to contact us when it does work. It makes me feel like it doesn't work for anyone, even though it obviously does -- we had more than 20k downloads last month...and less than 20,000 nasty emails
So, it feels good to hear a success story occasionally.Just an update on the new version: I decided there was a new feature I wanted integrated that was too good to wait for the next version. So I pushed this next round of testing back a couple weeks while we iron this out, which also gives us more time for some internal testing. Hope to have it finished by mid next week!
etotheipi and team, thanks for creating such an awesome and secure client!
My installation might actually be a bit below memory specifications, and may run slower than others', but it does work. The online machine has 4GB RAM, running 32-bit Linux (Fedora 20, upgraded using fedup from 17 -> 18 -> 19 -> 20). My two redundant offline machines, which are identical, are 455MHz Pentium III boxes with 256MB RAM, running Ubuntu 10.04 LTS and the Armory offline bundle. (I tried to install Ubuntu 12.04.3 on the offline boxes, without success. I installed Ubuntu from CD, and one of the machines apparently has a defective CD-ROM drive, resulting in a 40-hour install that ultimately succeeded -- luckily, there were no blackouts during those 40 hours, and the cats didn't unplug the machine ... 8^)
When I instantiated the second offline machine, I used only the paper wallet backup from the first offline machine to recover my wallet, and (of course) it worked like a champ. That was my own exercise in making sure this stuff really does work -- and it does!
My installation might actually be a bit below memory specifications, and may run slower than others', but it does work. The online machine has 4GB RAM, running 32-bit Linux (Fedora 20, upgraded using fedup from 17 -> 18 -> 19 -> 20). My two redundant offline machines, which are identical, are 455MHz Pentium III boxes with 256MB RAM, running Ubuntu 10.04 LTS and the Armory offline bundle. (I tried to install Ubuntu 12.04.3 on the offline boxes, without success. I installed Ubuntu from CD, and one of the machines apparently has a defective CD-ROM drive, resulting in a 40-hour install that ultimately succeeded -- luckily, there were no blackouts during those 40 hours, and the cats didn't unplug the machine ... 8^)
When I instantiated the second offline machine, I used only the paper wallet backup from the first offline machine to recover my wallet, and (of course) it worked like a champ. That was my own exercise in making sure this stuff really does work -- and it does!
Is it possible to issue command line arguments when using Armory? Such as "bitcoind listunspent"?
Yes, but you have to use armoryd (Amory Daemon) rather than the Armory application.
To run the Armory Daemon:
Build Armory from source code following instructions here: https://bitcoinarmory.com/download/building-armory-from-source/
You also need txjsonrpc from here: https://github.com/oubiwann/txjsonrpc
You can just clone it and put the directory right into BitcoinArmory
To play with it open a command line interface and enter:
python armoryd --testnet
Open another command line interface and send commands to it like this:
python armoryd.py --testnet listunspent
Jump to: