Testing version 0.90.99.4 for Windows, Mac and Linux*
I can confirm that this makes a huge difference compared to 0.90.99.3. The wallet that made the previous version unusably slow now works with almost no slowing down. Also the startup is now crazy fast. Almost a hundredfold increase in startup speed compared to any previous version I've used. But there's a problem with sending from the problematic wallet. I tried to make a donation to you guys but it always fails. I can't send coins to any other address from it either. Sending from my offline wallet works perfectly though. I tried broadcasting the transaction using blockchain.info, but it says that "An outpoint is already spent". Need your log file for to look at the send issue please. Edit: This could be related to a spent output with the wallet. You should rescan the transactions. No need to rebuild though. I expect the balance will change after the rescan. |
|
|
|
Nope.
And to be 100% honest, this really is performing faster than any time I have ever used it. Beyond actually working, there really is a noticeable performance improvement over initial installs with only a couple of small wallets. I now have 4 wallets restored, and it is running faster than times when I have restored a single wallet with only a couple of normal transactions for testing. Definitely make sure this fix gets into the new version!
EDIT:
I will note that when I initially loaded the watching-only wallet it worked, but no transactions were displayed (same version I sent you). I removedit and loaded the regular wallets, and all transactions were visible. Not sure what happened there. Maybe just a fluke, or maybe something worth checking out.
I think the speed up is to be credited to njaard and etotheipi work on optimizing the DB. As for the transactions, did you pick show all wallets in the drop down combo box? Some people have it defaulted to "my wallet" and that won't show you transactions for any wallet that you didn't mark as yours. |
|
|
|
That's a little scary but alright. Thanks for the donation. I get you had no issues sending either? |
|
|
|
Goatpig just pushed a change that might push people through the BDM-timeout barrier if they have these wallets with huge numbers of large transactions. Curious how the performance is after it gets past the synchronization, but at least you should get through it.
Zoella, rocks*, if you can, please checkout the latest 0.91-dev, make clean and make, then try it with your large wallets that were crashing (assuming you are on Linux... if not, we'll make a windows version after we know this solves it)
Booting VM, will get back to you soon! Yay, it's working! Woohoo! Wow finally... Let us know if there is an overall slowness feeled after the initial load. Oh and slam it with nastier wallets if you have any. |
|
|
|
At wallet corruption detection, should you choose to fix and need to unlock, Armory will not prompt again if an incorrect password is entered, simply note the error and present no option but to close the window. Would be nice if Armory presented the wallet name instead of ID tag there, too. As if I have any bloody idea what the password to 3CU1BLUti is...  Thanks for the report, I'll get on it soon. |
|
|
|
I can't reproduce the comment issue on my end. Try this:
1) Load you wallet in Armory offline.
2) Restore it from paper. This will rip the meta data from the wallet if it's currently loaded.
3) Load the restored wallet and see if the comments show up
Issue with that is it's an offline wallet, I don't really want to restore it from paper to my online computer. Can I just use a digital backup (Watch-only) from my offline computer? Or is there some way to do that without using the paper backup? I added this feature to save meta data on restores only. I should also add a way to just rip a wallet's meta data in a separate file, but I don't think that'll fit in 0.91 schedule's. If you use Linux and are willing to pull a side branch, We can work something and you be my guinea pig =P. However that will have to wait a few days, still working on the ledger entry issue. Currently you could move the WO to your offline Armory, and restore from there. This feature isn't meant to work with digital imports. Maybe it should. |
|
|
|
|
I can't reproduce the comment issue on my end. Try this:
1) Load you wallet in Armory offline.
2) Restore it from paper. This will rip the meta data from the wallet if it's currently loaded.
3) Load the restored wallet and see if the comments show up
|
|
|
|
The missing comments, are they Tx or Address comments?
Address comments are still there, transaction ones are gone. Do you have an approximate idea of how many comments were in your wallet? The wallet recovery tool displays that so you can compare, and let me know the comments are just gone or if its Armory not displaying them. OMG, it's actually working!  For the first time in ages I have a properly working Armory! I've had a ton of different problems before. They're all gone now. Great job guys! Not quite done with the ledger fixing yet but I'm glad to hear it works so far. |
|
|
|
|
The missing comments, are they Tx or Address comments?
|
|
|
|
leveldb missing error What error are you referring to? There was a leveldb bug that got fixed with the latest testing build (the one posted tonight) on Windows. Your post infers this bug occurs on Linux too, where it is built stock from google's source, so I'm bit curious now. Since I've started to pay attention to the Armory forum about a month ago I've also seen several threads on crashing for which little help was offered and no resolution provided. Most of these bugs are one and the same. Once we come to a fix the only thing we can do while we're working towards a release is to tell the users to wait for it. I guess it's better having someone doing that, but that's on our free time, so our presence can grow thin during busy times, like pre-release for these past 2 weeks. Also a lot of these users resort to sending us an email to our support channel, and those have a higher rate of resolution than what you can see here. Your assumption on Armory's stability is a little off however. What you are experiencing is obviously a wallet issue as it carries from OS to OS. Changing OS only changes how resources are delivered to Armory. While we had problems with that for a while, these were eventually fixed, and the users left with an unusable Armory are those falling in your category, with a wallet pointing at a lot of large transaction. It took us some time to isolate this issue but that we're on it, it won't last that long. For your information, I loaded Zoella's wallet in about 15sec. Coming from someone that simply can't get Armory to work, I'd say it's a step forward. Still implementing some fixes on that front as we speak. Back to the code now. |
|
|
|
Same here ... btw, do I need to update something now, when qt 0.9 is out?
No you don't. It's preferable that you do but 0.90 is compatible with bitcoin core 0.9.0 Just one tiny thing: Armory doesn't seem to find the daemon after installing core 0.9.0. Had to manually point it at Bitcoin\daemon. We're aware of this and this has been fixed in 0.91. As far the communication protocol goes, 0.90 is compatible with core 0.9.0 regardless |
|
|
|
I have 0.90 installed for ages (it feels). Never a single problem, no crash, no rescan, nothing. Works like a charm here on Debian.
Ente
Same here ... btw, do I need to update something now, when qt 0.9 is out? No you don't. It's preferable that you do but 0.90 is compatible with bitcoin core 0.9.0 |
|
|
|
0.91 is an improvement over 0.90 for sure. But we don't believe that it's a critical upgrade. I'm eating lunch with altoz right now and he also says he's had problems with 0.90 that required him to delete the .armory directory. I think you've got a lot of users who having problem but are just living with them instead of reporting them. i have had zero problems with 0.90 (zero crashes) and that's after putting it thru heavy testing. of course, my laptop has 16GB RAM with a huge HD in linux. Heavy testing? Can you take 10 transactions like this? http://blockchain.info/tx/e3aea19a966d103c4520530f6a8f9486b03d4cbe46deeeb56c4e72730fe83f2fI couldn't on any rig. These are the typical transaction that we identified bring Armory to a crawl, we're building a test case to identify possible inefficiencies. Worst case scenario we'll have to overhaul that part. |
|
|
|
|
There were plans to change that so im not sure if that was changed yet but at first the bitcoin core client would retrieve peers from a freenode irc channel.
|
|
|
|
Need a log file at this point. This is a sync issue most likely, however verifiy it is the right address you have in your wallet ledger on the Armory side, and send up a log at support@bitcoinarmory.com with a link to this thread. |
|
|
|
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?
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. |
|
|
|
 I'm not in a hurry anymore. I exported a private key and got the coins that I needed out, so I can wait for the next version. Thanks for the work you are doing! Armory has some great features and I'm looking forward to using a stable version in the future. Thanks for the wallet, it loaded on first try with 0.91-dev, so Im hoping you will have the same smooth experience with the upcoming test build |
|
|
|
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? 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. |
|
|
|
|
Start Armory in expert user mode, go to your wallet property window, pick backup center and chose export key list. You'll see all your private keys.
|
|
|
|
|
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?
|
|
|
|
|
Show Posts
