BitcoinArmory

BitcoinArmory copied to clipboard

Is it intended to do so?

Can't the transaction index be stored and the history only scanned from the last point?

Also, I run bitcoind with the -txindex option, is this the same as the transaction index Armory calculates? Because if so, it happens twice and it should be possible to let Armory use the same index as bitcoind.

Yes, it's the way it was designed. It was not a problem when it was created 18 months ago with a 300 MB blockchain. Obviously it is now. I haven't changed it yet because it may be inconvenient, but there's a certain robustness associated with forgetting and rebuilding every load. The tradeoff has long been consumed, though.

I'm working on the new database design, right now, to do exactly what you just suggested. There's a bit of extensibility I want to build into it, so it's not as trivial as just throwing everything on disk.

Fear not, it's being worked on.

Great to hear that! It's really comforting to know that Armory is still in active development and to get reactions so quickly here.

If I had some more spare time, I'd definitely try to contribute, but I don't have to time to get involved right now.

Are you the only active developer of Armory, or are you just the lead one? Don't you have a mailing list or so where developers can discuss design decisions?

I wanted to open another issue with the question if it is normal that Python reaches 2.3GiB memory use when Armory is running, but I assume that has to do with the same problem as this issue and will be solved as soon as Armory uses an on-disk database?

The RAM usage is fixed in the same upgrade. But don't hold your breath. I decided if I'm going to redo the blockchain utilities, I should Do it the Right Way, and accommodate all the future Armory variants (I want reduced modes, super nodes, and flat-out lite-mode)

Sounds ambitious!

I'd really like to help. Sadly, work for school and my responsibility in our local youth movement prevents me from diving into projects for now. Who knows in a year or two we'll speak again...

Not that we won't speak again sooner, I feel like I'm one of the most active issue files over here :D

My laptop is dying because of this issue. I'm glad to see it's being fixed. Thanks

Is this fixed yet?