|
Known bug, fixed in the upcoming release.
|
|
|
|
|
Armory needs bitcoind to auto manage. Ima go ahead and assume what you have in /usr/bin is BitcoinQt. Do a whereis bitcoind, and point Armory to that.
Or do not point it to anything and let it look at default locations, it is usually quite efficient at that on Ubuntu.
|
|
|
|
|
Go in Expert mode, and make sure you have clicked "Include Unused (Address Pool)"
With the options you chose, you are only displaying visible addresses, which you can reveal one at a time clicking on "Receive Bitcoins" in the Wallet's Properties Dialog.
|
|
|
|
|
This is what I deal with most of the time on the support channel:
1) bitcoind is installed in a non standard folder. You need to point that to Armory in the File -> Settings menu. On Windows, in the current version, you have to point at the folder containing the daemon (bitcoind.exe), not just the top Bitcoin installation folder. This bug will be fixed in 0.91
2) The blockchain is in a non standard folder. This is an issue regardless of bitcoind (auto managed) or BitcoinQt (no management). You need to point Armory to the raw blockchain files, either through the Files -> Settings menu, or by using the --satoshi-datadir command line argument
3) Some users have modified bitcoin.conf, usually to reduce connectivity. Armory connects as a node so bitcoind needs to allow it in. The common approach is to add listen=1 in bitcoin.conf. I prefer bind=127.0.0.1. Worst case scenario, getting rid of the .conf (rename it to something else for instance) fixes the issue.
Note that in auto manage, Armory tries to query bitcoind status through the JSON-RPC API, and it sets its own log/password in bitcoin.conf for that purpose.
4) "It's been sitting here for hours synchronizing". By far the most annoying state to fix, since I have personally never ran into it, and I have sync'ed the blockchain and Armory's DB from scratch quite a few times. Same goes with the other devs, we just don't run into these, so we don't really get to observe the bug.
There are 5 cases essentially:
4.a) Some users just don't realize how long it takes to download and verify the blockchain. Thats 10-20% of the user base.
4.b) A certain amount of users (can't really give you figure because they get mixed with case 4.d) do not properly set their system clock, resulting in bitcoind never fully syncing with the network.
4.c) Syncing Armory without a wallet loaded. Don't do that. Create a mock wallet if you have to.
4.d) Corrupt DB. Armory's DB somehow got corrupted. Most users experience an Armory freeze and/or crash when it runs into the corrupt data. At this point start Armory in offline mode (use the --offline command line argument) and click on Help -> Rebuild and Rescan Databases. If Armory still crashes, you have to manually delete the databases folder in Armory's datadir. I'd say 10% of our users run into this.
4.e) Messed up blockchain. This is our main concern currently. Even though bitcoind reads the raw files properly, Armory chokes on them somewhere. Our issue is that we never got a blockchain in that state to observe the issue, so we haven't gotten around fixing it. We have yet to find someone willing to upload 14GB worth of blockchain to us either =P. At any rate, the solution to this issue is to delete the blockchain raw files and let bitcoind resync. About 10-15% of our user base runs into this.
|
|
|
|
|
That's an interesting point. You should try bind=127.0.0.1 instead of listen=1
Also, I would personally use Tails rather than just Tor, to guaranty all traffic goes through Tor.
|
|
|
|
0.90 on Win8.0 64 bit (brand-new HP 2000 notebook) says "This app can't run on your PC". Any options or should I return it?
Did some searches but didn't find much
Thank you!
Is it one of those lightweight windows they put out for tablets? |
|
|
|
|
The windows bundle is stand alone by nature. Offline bundles are for Debian/Ubuntu only. With windows installed, you only need the Armory Windows installer to run offline Armory off of it.
|
|
|
|
Is it possible to somehow get a list of 1,000 pre-generated addresses of an Armory wallet?
I know I can use the "Backup Individual Keys" function and then click "Include Unused" but this will give only about 100 pre-generated addresses.
Is there a way to extend this to a 1,000 addresses?
Start Armory in expert mode. Select a wallet and go into properties, then click the number in front of "Addresses used" |
|
|
|
Could you please post a list of the common setup issues that you receive? Please rank them by frequency, and I will tackle them in that order.
1) Can't get Armory to sync. There's no 2. |
|
|
|
Why? All the help most need is already available at the Armory website. The developer is also available here on the forum for any questions not already covered.
95% of the support emails are about common setup issues. We can spend more time developing Armory if those users can get Armory working without having to ask for our assistance. |
|
|
|
I noticed the VM's clock was off by 2 hours. Strangely enough small transactions go through fine.
2 hours off the clock can be very significant for BitcoinQt. Is Armory showing the right amount of confirmations now? |
|
|
|
|
aasl: There isn't really a feature supporting this use case right now.
coraz and K1773R: I agree we could make the coin control UI a little friendlier.
|
|
|
|
The Armory won't work until the bitcoinQT deamon is all loaded up and synced. So that wasn't the issue. Armory won't even show transaction history until it finishes syncing with bitcoinD anyway so I can't check the details until I at least see the transaction there. But according to blockchain and blockexploer 277156 was where that bitcoin was and it all looked good on my end. Having said that, I came from using Electrum, and never experienced these issues. I unfortunately had to dump .88 version of Armory because of the resource issue and just started to use .99 recently, but I apparently just keep coming up with these little quirks and anomalies that don't make sense. Even right now, 3 hours later Armory still says 4 confirmations on that transactions and blockchain and explore both have over 25. I'm just wondering where the heck is it picking up 4, and the bitcoin daemon is all updated on my end here.
Turn off bitcoind auto management, start BitcoinQt yourself, then check block height in both BitcoinQt and Armory. Again, make sure these are the same as what you can see online. You have to keep in mind that BitcoinQt/d constantly receives block data, that it then passes to Armory. You are most likely quite a few blocks behind on bitcoind. |
|
|
|
|
I don't quite understand the question here. However, if you have disk space issues, you can configure both BitcoinQt and Armory to fetch and save their data in a folder of your choice through the -datadir switch with BitcoinQt and --datadir with Armory
|
|
|
|
|
Armory depends on BitcoinQt for its networking. Your case sounds like either BitcoinQt was off or it wasn't updating. Next time make sure the block height displayed by BitcoinQt is the same as what you see on blockchain.info or blockexplorer.com. Then compare that value to the one displayed in Armory.
Any divergence there should give you a better idea of which part is at fault.
|
|
|
|
I'm a new user of Armory, trying 0.90, and it's crashing consistently before I have even imported my wallet. I've already had Bitcoin-QT running to download all the blocks. I can send you my log files, as well, if you'd like.
Would like the logs indeed. Curious to see which bug this is. It can't be the same as justusranvier's, for you have no wallet loaded. |
|
|
|
Yeah that failed pretty hard, I'll try to get it fixed. Thanks for the report. |
|
|
|
|
I dont see any either. Send us the full log, and the cpplog too. I may find some hint in there.
|
|
|
|
If I create an Armory offline wallet (or online for that matter) and let it sit for 10 years (or any amount of time) what happens if Armory is discontinued? Will I still be able to access my bitcoins though another service using my wallet credentials? I currently have an offline wallet and want to make sure I can access those funds if Armory goes belly up.
Also I fired up Armory online, imported a new watch-only wallet and the database build said 81 months with version .88. I just had the online version running yesterday but 81 months had to be wrong regardless. I have a pretty fast quad-core computer FYI. Exiting Armory and running it again fixed that problem.
Thank You
' Armory's source is on github. Correct me if I'm wrong, but I think they have a politic of never deleting any file. You can access all older versions as well, as long as you can find the particular commit. And I don't think you can destroy just shut down a repo. So the source will be available as long as github is around, and I don't expect them to go down unless they take the entire internet with themselves. |
|
|
|
|
The ID is extracted from the first few bytes of the first public address in your wallet. That value is then encoded in base58, so it may not necessarily be 9 characters long.
ID collisions is a possibility but rather abysmal. The chance of actual wallet collision is the same as 256 bits integer collision, i.e. not gonna happen.
|
|
|
|
|
Show Posts
