Finally hit the $3k mark! Sure, I don't think I can make the full $12k, but $3k is certainly enough to make a difference here. And I'll be getting an article on BitcoinMedia soon, so that will hopefully draw in some folks not on the forums
If not, I may have to commit to using a large chunk of unpaid leave instead of actually going part-time... nonetheless, any full-day chunks of time I can spend on Armory while the house is empty is when I make the most substantial progress...
So there's a lot to respond to here... amazing what accumulates over the course of one day!
@ Muyuu, Holliday & Cypherdoc,
Armory wallets are completely different than Satoshi-client wallets, and for a very good reason: the Satoshi-client wallets are terrible. They require a DB engine, which requires an extra library, and the DB itself is what was responsible for the
wallet-not-actually-encrypted bug. Supporting Satoshi wallets is a step backwards, and a substantial time investment. Not to mention, there has been some talk recently among the devs of switching away from the current Satoshi wallet format -- so I feel like it's not worth it.
However, I will support
migration. I will leverage Joric's pywallet tool to help pull all the private keys out and import them into an Armory wallet. It's the best I can do amidst my priorities.
In the meantime, the thing stopping users from manually doing this, is the lack of a bulk-import feature in Armory. It was already part of my RAM-upgrade, but that's not going to be done for a while (but will be necessary when it takes 30s per address import). Until then, I can probably put together a super-quick python script that will simply import a list of private keys in a specified Armory wallet -- then the determined users can use Joric's pywallet to dump the private keys. Or maybe I will send that script to Joric: maybe he would be up for making an import tool like this...
@ RassahThis is something I've thought about, but there are a lot of risks associated with holding a pruned blockchain. I believe it will have to be done eventually, but that there will also be a network-level accommodation for it: such as including unspent-tx-out-tree-hashes in the coinbase transactions, so that nodes can verify their pruned blockchains against other nodes. I am wholly in support of such a scheme if it can be made to work, but I feel like there's going to be a big paradigm shift to make this doable in Armory without it (and maintain a high confidence in the security of the application)
Regardless, I don't see this as a solution to the RAM problem, because I don't want to bank on the pruned blockchain taking up less RAM than some arbitrary system. One day Armory works, the next day someone creates a ton of unspent outputs and Armory won't load anymore. I have a solution for the RAM issue (without pruning), that I have already confirmed works in Linux, and I don't see why it wouldn't work in Windows. I just have to get a solid chunk of time to get it all implemented, debugged, and tested. It'll be a couple weeks.
@ OtohIt's easy to say in hindsight I should've picked a different name. Sure, the word "Armory" has different initial impressions to different people, but in the end it was concise, unique, memorable, and held some meaning related to what I wanted. Just like "Google" (googol) or "Oracle", one day it just becomes a name, instead of a common word doubling as a name.
@ IndeminfiedLol. Thanks for your actual donation, and bullying others to donate, as well. Perhaps you can be the official bouncer for this thread