Quote from: Zoella on March 19, 2014, 03:09:47 PM

Quote from: Rock6.3 on March 19, 2014, 02:06:59 PM

Quote from: etotheipi on March 19, 2014, 05:25:46 AM

Ugh, looks like it worked, but your blockchain wasn't fully up to date. The 0.4 left is the last three outputs received by that address.

Also, I can see that you did fall into this category I asked about (users don't always know if they are in this category). Each transaction received by that address has tons of outputs. The first one has 1,400 TxOuts of which you are only one.

Armory has a known inefficiency when it comes to transactions that huge, and you have a wallet full of them, so that's as bad as it gets. The good news is most of the processing that's slowing it down turns out to be non-critical (it's for associating address and tx labels with the rows in the ledger), but still important. We might see if we can find a way to disable it on wallets in this category, of if maybe we can just find a more efficient way of doing it.

For now, sweeping should work as long as Armory is fully synchronized. Scanning the blockchain to sweep the addresses should work at "normal" speed, it's just populating the main window ledger that takes forever and Armory trips over itself while it waits.

If I understand your statement correctly, you are saying that Armory is a bad wallet choice for mining pool participants who are paid out in batches.

I guess it depends on what mining pool. My wallet that collects my Eligius payouts has been OK (but I will have to import and check again). The addresses I'm having problems with in this wallet are scrypt coin switching pools (PoolWaffle, Middlecoin, etc.).

I would definitely think resolving this would be a priority since so many of these types of pools have popped up recently. Then again, it may just be my bias reflected by me being caught in the situation. Definitely not fun.

I do hope it is a priority since I mine on WafflePool and my Armory BTC Wallet is broken.