Topic: ... (Read 9159 times)

Can't see anything wrong in Armory's log. Last lines:

Not sure if I am at the right place/post, but I just started to use Armory and I am seeing the same problem.

I start Armory, and nothing happens, not splash, no gui, nada. It starts bitcoind in the background though. Bitcoind is at a default place and is synced.

If I kill Armory and restart, it starts up fine but complains about bitcoind already running. If I kill bitcoind first, Armory also starts up, but in offline mode.

Running Ubuntu 12.04 64bit, armory 0.90-beta (from official deb) and bitcoind 0.8.6

Just hit "Receive Bitcoins" a few times and it will calculate the next few addresses.  I thought Armory would do that automatically when it found money in "future" addresses in your wallet, but I guess not.  It does include them in the blockchain scan, but doesn't display them because it thinks they are "unused."  Definitely a bug.

That clarified some things - thanks!


I got a wallet and 4 addresses in there. I have made 3 translations - each time I have send money to an address A. Now when I open armory I see only 3 addresses B, C and D, but I don't see address A.
I see 3 incomes. My wallet show balance properly - but when I click on it I see only 3 addresses B,C,D and no A with my BTC on it. Is that OK ?

https://imageshack.com/i/5iw01ej


https://imageshack.com/i/046onaj

The root key and the chain code are not the same thing.  The root key together with the chain code allows Armory to generate an essentially infinite sequence of private and public keys (this is used in ordinary wallets).  The first public key together with the chain code allows Armory to generate all the public keys, but not the private ones (this is used in watch-only wallets, they only contain the public keys, so you can see the BTC but not spend them)


Both the digital and paper backups that Armory produces contain the root key and the chain code, so the backup protects all keys that Armory has generated in the wallet, and all keys Armory will generate in the future.  The backup of "individual keys" is only for the very special case that you have manually imported keys into you wallet that are were not generated by Armory.  That is a rare thing to do (and rarely a good idea).

HI! I downloaded armory a week ago and its loading time its still a pain in the ass. I take forever to work, even when you close it and open again. Maybe its because I have encrypted (truecrypt) whole drive... dunno you must do something with this because its non use for most users (1-2 hours of loading time, no thx).

I have question about my private key and public key - where I can peep them in program (I can see them when I do paper backup - first 72 marks its my private key - root key, and second 72 marks is a public key - chain code, right ?)?

Also when I do a digital backup my addresses are not backup? Cause why there is another options to backup my individual keys? Could you explain it to me? If I don't do a backup of my addresses I lose the money in them?

Thanks for understanding those noob question, I'm waiting for answer

If you switch to the "testing" branch, you'll get the new version, which has it's own set of issues, but works very well if you are careful (don't interrupt the initial DB build or scan).  So far, I have experienced zero issues on both my Linux and Windows testing versions when I let it do its thing. 

The initial DB build takes 30-90 minutes, and 15-30 minutes for the subsequent scan.  After that, it's about 30 seconds to startup (plus a couple minutes if you haven't loaded it in a while and it has a lot of tx history to synchronize).

I built direct from github on Ubuntu and Armory still performs a lengthy scan each time it loads.

Despite the optimistic messages (2 minutes left ... 1 minute left ... 15 seconds ...) it generally takes about an hour.

I have also discovered that after performing a spend (offline wallet mode) armory will crash silently. I have seen this twice. I can provide logs on request, this may be due to Armory believing BitcoinQt to be out of sync, when it is not.

Despite these niggles, Armory is by far my favourite tool for keeping BTC safe

I'm experiencing the same problem. If i close Armory and i run it again it rebuilds the database again. Is my blockchain corrupted? What can i do?

By the way is there a way to change the default .wallet location and run the wallets from another folder?

I think you really need 16 GB RAM to run Armory 88.1 with the current blockchain. 8 GB is barely enough. Upgrading from 8 GB to 16 GB RAM worked for me.

Read two posts up

As an additional data point:

I had to install the newest version 0.88.1 on my Windows system since the older version ran out of RAM and crashed.

Current system:
MacBook Pro booted into Windows 7
16 GB of RAM
Armory consumes 3.8 GB of RAM!

At this point, Armory is already approaching the point at which it will exceed the memory usage of most consumer PCs, which are still being sold in the 4GB or less range.

I would advise that the memory usage must the first priority in development, or else nothing else will matter.

The scanning doesn't take too long on my desktop (about 4 minutes) but it sure is going to be a delight to see faster startup. What's the right branch for testing out the linux version you mentioned earlier?

Thanks for your hard work!

I just got the new branch working in Windows, finally.  And a lot of issues I was having are resolved.  This means I can probably have a pre-testing version available in the next day or two.  However, I wouldn't recommend it for regular use, since it will be pretty rough around the edges.  But it will be sufficient for getting your coins out if you've had them stuck in Armory for a while.

Of course, I keep making statements like that and I haven't been able to stick to them.  I really should say "next week" and then everyone will be happy when it's Saturday   I'm not going to rush it, but all the stuff really is working quite well, including the cool new backup center...

Is there an ETA? OR "when it's done"?

Unfortunately, the blockchain corruption is probably a Bitcoin-Qt problem, which I don't have much control over.  Nonetheless, you do avoid all that with Electrum.  But rebuilding probably won't fix it.  You have to add checklevel=2 to your bitcoin.conf or upgrade to 0.8.5.  Or maybe it really is Bitcoin DB corruption...

Give it another shot when I get the new version released.  You will probably be pleasantly surprised by it.

Unfortunately I'm in the middle of switching over to Electrum now. Armory maybe loads half the time and when it does it takes about an hour to get a proper balance. Not sure what's up with this wallet, but it's more work and time than I really have to spend. I double click on Electrum and it loads/syncs in about 30 seconds, and doesn't need huge amounts of memory or speed to work. I'm not bashing Armory, I actually wish I could still continue to use it, but the past 5 times when I needed access to my BTC I wasn't able to access them. Right now my index got corrupt "somehow" and has to re-build itself so I'm letting that run over night, then just sending my BTC to my Electrum address. Too bad, the potential and security was there but the reliability wasn't. Good luck with future upgrades.

Well there's actually a pre-testing version available for Linux now, that you can technically checkout and use.  It has all the above properties, including 250MB RAM usage and saving scan data between loads.  But importing/sweeping/restoring addresses & wallets is a bit funky.  If you only do those ops while in offline mode, then it will rescan next time it's online, and then shouldn't rescan again until import/sweep/restore more stuff.  So far I've had it running for a week on my dev system, and it's stable.  But those rescan/rebuild ops are giving me more trouble than I was expecting.

Today I'm going to see if I can get it working in Windows.  It will have the same caveats, but at least it will help people move their money if they've been shut out up to this point.  
 
For reference, starting a company is a lot of work!   That's why this has taken me so long -- I've been thoroughly distracted with endless paperwork, negotiations, contract terms, lawyers, recruiting, finances, setting up bank accounts, etc.  I've been able to do some development in between, but obviously not at the rate otherwise.

So yes, I said these thing back in May, but I also hadn't anticipated going through such a grueling investment deal.  But now people can start believing me, because I actually have a version out there they can use

Didn't you say that in March?

If its true, all I can say is...THANK FARK FOR THAT!

The next version has solved all of these problems (currently in the ramreduceleveldb and rrld_planB branches).  It's not quite ready for testing, but should be very soon.  Armory now builds the database and scans it on the first load only, saving everything between loads.  And only uses like 250 MB of RAM (which should be independent of the blockchain size). 

Obviously, this is a huge step up from where it currently is.  I just haven't had the time to overhaul the relevant code until now.