FYI: I don't have a problem coming up with a solution, it just hasn't been as important to me as getting some of the more advanced features implemented. I'd rather 40% of people get functionality that they can't get anywhere else, than 90% can use an "average" program.
But priorities have shifted due to the excessive size of the blockchain, and it's top priority to resolve this. I have lots of plans: not having to rescan everytime, having lite versions, pruned versions, electrum-style-remote-server versions. It's not a lack of ideas, it's a lack of time
But hopefully the whole rescan-every-load thing, will be out of the way in a few weeks. I'm finally making the data persistent, and dropping RAM usage by an order of magnitude. Unfortunately, the usability issues hit me faster than I anticipated so I'm scrambling to get it together. But it's happening.
But priorities have shifted due to the excessive size of the blockchain, and it's top priority to resolve this. I have lots of plans: not having to rescan everytime, having lite versions, pruned versions, electrum-style-remote-server versions. It's not a lack of ideas, it's a lack of time
But hopefully the whole rescan-every-load thing, will be out of the way in a few weeks. I'm finally making the data persistent, and dropping RAM usage by an order of magnitude. Unfortunately, the usability issues hit me faster than I anticipated so I'm scrambling to get it together. But it's happening.
Great to hear your already thinking about it! I know developing software on the fly isn't always easy or fun, but I think this could improve armory usefulness by an order of magnitude. I'll find your donation link, and send ya some beer money
Thanks for the reply and all the hard work you've put into armory