Sorry in advance for being blunt, but when it comes to releasing 0.91 you guys really need to shit or get off the pot.
Right now you don't have any viable downloads on your website. The 0.8x series is too resource-intensive for most users, and 0.90 is unusably crash-prone.
A year ago, I could point people in this situation: http://www.fr33aid.com/1511/fr33-aid-bitcoins-stolen/ at your website and know they'd find something there they could download and use, but that hasn't been true for the last six months and I don't see any particular acknowledgment of this or urgency on your part.
It's not a problem for me personally since I can just grab the 0.91 branch from Git, but a lot of people who can't are losing Bitcoins because there aren't any good usable cold storage solutions any more.
New features are great to have, but they shouldn't delay you having a minimal viable product out, where "minimum viable product" is defined as "an application that lets you send and receive bitcoins from cold storage without consuming obscene amounts of RAM and also doesn't crash every few seconds."
Topic: Armory - Discussion Thread - page 63. (Read 521749 times)
Just an update, I was able to completely sweep another key last night. There may be other issues with the sweep function though (unless it is simply the batch transaction issue again), but I can only do one key at a time, and I have to restart Armory in-between attempts. For some reason, I have not been able to succeed at sweeping multiple keys in a single go, nor any keys after a successful sweep. Hopefully I can finish up today though, thanks for all the help!
Did you try using the "Multiple Keys" sweep option at the top? It was designed for this
If you don't mind doing one test for us, I just pushed the disablecomments branch to the BitcoinArmory repo. I removed all the logic I think is slowing you down. If our hypothesis is right, this will work. This is the best I can do without getting your watching-only wallet.
P.S. --
I really appreciate you being so patient! Seriously, thanks. Hopefully, as we go back through some other support requests, we'll see that most of them are due to this. Admittedly, I don't do any mining, or have any enormous tx like this in my ledger (and apparently no one on our team, either). Also, this did come up 18 months ago, and I made a huge efficiency fix that was supposed to fix it. But apparently not efficient enough...
I did try the multiple keys, but everything just always timed out/crashed.
I can confirm there are still problems with the sweep (before your disablecomments update). I know my blockchain is up to date, but another address is failing to grab all transactions.
https://blockchain.info/address/1JkP7cCqA9bxRfzYGLLi6qTvSnQ8sx8PRm
When I try to sweep this address, Armory only sees .08330224 BTC. This is several transactions behind again, even though I know I have a sync'd chain.
I will download the update and see if that helps!
BTW, other than this one issue (which for me is an admittedly big issue), Armory is hands down my wallet preference. Hopefully a solution can be had quickly. Once I've swept the remaining coins I'd have no problem giving you the old wallet for testing if you want it, since it should still have all the old transaction issues.
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.
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.
Just an update, I was able to completely sweep another key last night. There may be other issues with the sweep function though (unless it is simply the batch transaction issue again), but I can only do one key at a time, and I have to restart Armory in-between attempts. For some reason, I have not been able to succeed at sweeping multiple keys in a single go, nor any keys after a successful sweep. Hopefully I can finish up today though, thanks for all the help!
Did you try using the "Multiple Keys" sweep option at the top? It was designed for this
If you don't mind doing one test for us, I just pushed the disablecomments branch to the BitcoinArmory repo. I removed all the logic I think is slowing you down. If our hypothesis is right, this will work. This is the best I can do without getting your watching-only wallet.
P.S. --
I really appreciate you being so patient! Seriously, thanks. Hopefully, as we go back through some other support requests, we'll see that most of them are due to this. Admittedly, I don't do any mining, or have any enormous tx like this in my ledger (and apparently no one on our team, either). Also, this did come up 18 months ago, and I made a huge efficiency fix that was supposed to fix it. But apparently not efficient enough...
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.
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.
Just an update, I was able to completely sweep another key last night. There may be other issues with the sweep function though (unless it is simply the batch transaction issue again), but I can only do one key at a time, and I have to restart Armory in-between attempts. For some reason, I have not been able to succeed at sweeping multiple keys in a single go, nor any keys after a successful sweep. Hopefully I can finish up today though, thanks for all the help!
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.
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.
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.
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.
Ahh, I thought you meant tons of transactions directly to the address, not single transactions to tons of different addresses. I kind of figured this would be a common thing for pooled mining?
So, regarding the blockchain being up to date. The wallet says it fully synced, showing 291259 blocks. The last transaction on that address was block 290240. You're right that the last three didn't get scraped, but that seems kind of weird? I'll try it again and see what happens.
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.
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.
Well it sort of worked on one address. For some reason it left .04 BTC?
I received an invalid transaction error, but it seems to have worked (except for the .04 BTC). Thoughts before I try it on other addresses or retry on this one for the remainder?
https://blockchain.info/address/1JaZiwrMyfYXiNuAdq6cBknJHtQAQFCxUg
I received an invalid transaction error, but it seems to have worked (except for the .04 BTC). Thoughts before I try it on other addresses or retry on this one for the remainder?
https://blockchain.info/address/1JaZiwrMyfYXiNuAdq6cBknJHtQAQFCxUg
We literally just fixed a bug in the sweep code, like 2 hours ago. Pull 0.91-dev and try again.
I'm not convinced this won't work. If anything it will help debug the problem. This will probably work for some of the keys, and maybe one in particular it will fail.
I'm not convinced this won't work. If anything it will help debug the problem. This will probably work for some of the keys, and maybe one in particular it will fail.
Will give it a shot.
Making. Should I redownload the blockchain as well?
Nope. Just pull the latest 0.91 and try sweeping again
We literally just fixed a bug in the sweep code, like 2 hours ago. Pull 0.91-dev and try again.
I'm not convinced this won't work. If anything it will help debug the problem. This will probably work for some of the keys, and maybe one in particular it will fail.
I'm not convinced this won't work. If anything it will help debug the problem. This will probably work for some of the keys, and maybe one in particular it will fail.
Will give it a shot.
Making. Should I redownload the blockchain as well?
OK, frustrated to the point where I'm ready to create a new wallet. I'm trying to sweep in the BTC from the old wallet, and it is not working. Here's what I'm doing, please tell me if I'm missing something...
1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes
Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).
Thoughts?
1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes
Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).
Thoughts?
To sweep, Armory needs to know the available UTXO for the private key. To do that it goes through the same scanning process as if these private keys were loaded with your old wallet. This method will not help you.
Wonderful. So what method helps me recover the BTC in a 1.35c paper backup?
We literally just fixed a bug in the sweep code, like 2 hours ago. Pull 0.91-dev and try again.
I'm not convinced this won't work. If anything it will help debug the problem. This will probably work for some of the keys, and maybe one in particular it will fail.
I'm not convinced this won't work. If anything it will help debug the problem. This will probably work for some of the keys, and maybe one in particular it will fail.
OK, frustrated to the point where I'm ready to create a new wallet. I'm trying to sweep in the BTC from the old wallet, and it is not working. Here's what I'm doing, please tell me if I'm missing something...
1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes
Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).
Thoughts?
1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes
Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).
Thoughts?
To sweep, Armory needs to know the available UTXO for the private key. To do that it goes through the same scanning process as if these private keys were loaded with your old wallet. This method will not help you.
OK, frustrated to the point where I'm ready to create a new wallet. I'm trying to sweep in the BTC from the old wallet, and it is not working. Here's what I'm doing, please tell me if I'm missing something...
1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes
Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).
Thoughts?
1) export key list from old wallet
2) open wallet, select import/sweep
2) choose sweep, single key
3) enter base58 key from export list (for an address I know is not empty)
4) verify corresponding address is correct and click yes
Armory then requests to scan the blockchain for another 30 minutes, creates a new address in my new wallet (presumably for swept funds), and then...nothing. This happens with every private key from the list I've tried. I've verified the address is not empty via blockchain.info (when it's up).
Thoughts?
Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?
After/During the creation of the file. I was watching as the progress bar moved to about 50%, then switched away for another task. When I returned the only thing open was the terminal window. That error was the last thing in the terminal window when Armory crashed and returned me to a prompt.
Then it probably happened at the end. Was the process particularly long? Like over a minute?
Quote
Connected (29XXX Blocks)
Did you forget a X or are you showing only 29k blocks?
getSpendable errors are also just a symptom of a locked up BDM. Definitely the wallet. Consider sending us the watching only, it would make this whole process entirely faster, and I could push the fix with the next release.
I would guess about 30 seconds, and yes, left off an X. With no wallets, showing 291229 right now.
Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?
After/During the creation of the file. I was watching as the progress bar moved to about 50%, then switched away for another task. When I returned the only thing open was the terminal window. That error was the last thing in the terminal window when Armory crashed and returned me to a prompt.
Then it probably happened at the end. Was the process particularly long? Like over a minute?
Quote
Connected (29XXX Blocks)
Did you forget a X or are you showing only 29k blocks?
getSpendable errors are also just a symptom of a locked up BDM. Definitely the wallet. Consider sending us the watching only, it would make this whole process entirely faster, and I could push the fix with the next release.
Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?
After/During the creation of the file. I was watching as the progress bar moved to about 50%, then switched away for another task. When I returned the only thing open was the terminal window. That error was the last thing in the terminal window when Armory crashed and returned me to a prompt.
Save sequence is not an error in itself, it's a clue as to what the user may have done with his wallet. In this case it doesn't indicate any error, your wallet is fine. The decrypt key error is significant. I'm not sure I understand though: did the decrypted backup error happen before or after the wallet file was created?
Jump to: