Armory 0.93 testing release! (with 0.05 BTC bug bounty)

[oneoctet]

If you shut down Armory while it's building its database, when you reopen it (even using --offline) and double-click on any address of any wallet it crashes.

Code:

(ERROR) -- Traceback (most recent call last):
  File "qtdialogs.pyc", line 1968, in dblClickAddressView
  File "qtdialogs.pyc", line 3783, in __init__
  File "CppBlockUtils.pyc", line 1927, in getSpendableBalance
RuntimeError: Cannot start transaction without db env

[1714607331]

1714607331

[1714607331]

1714607331

[1714607331]

1714607331

[1714607331]

1714607331

[goatpig]

Also, an update on the transaction scanning: I moved it from my HDD to SSD and now the estimate is 8 hours, and disk IO is about 30-80 MB/s. Maybe there's a lot of random access going on, not just linear access? That would explain why it's running so much faster, even though my HDD's linear access is much higher than 1-3 MB/s.

LMDB doesn't keep much of its data sequentially as opposed to LevelDB, and that's demolishing HDD speeds. I'm working on some optimizations for HDDs.

[japerry]

Also, an update on the transaction scanning: I moved it from my HDD to SSD and now the estimate is 8 hours, and disk IO is about 30-80 MB/s. Maybe there's a lot of random access going on, not just linear access? That would explain why it's running so much faster, even though my HDD's linear access is much higher than 1-3 MB/s.

LMDB doesn't keep much of its data sequentially as opposed to LevelDB, and that's demolishing HDD speeds. I'm working on some optimizations for HDDs.

I for one am greatly awaiting this optimization!  I was at 66% on "Building Databases" and it said 9 hours left. I'm at 71% now and it says 3 days. I'm not complaining. I know it's beta code. I'm willing to wait because Armory is a great product and I believe in it. You know the old saying... To paraphrase "Good things come to those who wait"

[goatpig]

Also, an update on the transaction scanning: I moved it from my HDD to SSD and now the estimate is 8 hours, and disk IO is about 30-80 MB/s. Maybe there's a lot of random access going on, not just linear access? That would explain why it's running so much faster, even though my HDD's linear access is much higher than 1-3 MB/s.

LMDB doesn't keep much of its data sequentially as opposed to LevelDB, and that's demolishing HDD speeds. I'm working on some optimizations for HDDs.

I for one am greatly awaiting this optimization!  I was at 66% on "Building Databases" and it said 9 hours left. I'm at 71% now and it says 3 days. I'm not complaining. I know it's beta code. I'm willing to wait because Armory is a great product and I believe in it. You know the old saying... To paraphrase "Good things come to those who wait"

Obviously we're not gonna release a DB in a poor state.

[jammers]

I hadn't used my computer today, but this evening switched it on and tried to get armory up and running. Went through everything else fairly quickly, but now stuck for the last half hour like this :/

[Carlton Banks]

Old minor bug, but still present in 0.92.99.1 :

When using the soft-keyboard (all 3 types) to input wallet unlock passphrase, use of the & character generates two characters instead of one (represented by two * symbols in the input box). Passphrases with any & characters cannot be input using the soft keyboard.

[jammers]

lol



and this is after going for an hour. the last leg is really struggling

[jl2012]

It does not mention BIP32 Hierarchical Deterministic Wallets. So it is not supported yet?

[TimS]

Armory has finished scanning transaction history! The dialog announcing that seems to be responsible for crashing Armory, though.

I saw the dialog saying "Blockchain loading is complete." etc. I didn't check the box, and I clicked Ok to close it, and noticed Armory was no longer running. No error in the logs, logs not even updated in several minutes.
The next time I tried to start Armory, I didn't see that dialog, the Armory window opened, and it crashed with the same sort of nondescript error window shown here: http://imgur.com/a/t63L7
I tried to start Armory a few more times, and each time it crashed after I clicked Ok in that dialog. So I checked the box to not show it again (I think it crashed one last time here), and opened Armory again, and it worked this time: I can view balance, all seems well. Sending my logs to contact@bitcoinarmory.com right after I post this, in case it helps find the problem.

[etotheipi]

Okay, obviously some rough edges with this release.  We knew that we were going to have to get more people poking it with a variety of hardware configurations, to get it robust.  We still have some work on that front.

However, we've reverted/fixed a bunch of the unicode issues.  And a few of the bugs already reported.  Want to make sure that people who are reporting are not reporting bugs that were related to the unicode stuff.

Here's the next release:

Armory 0.92.99.2-testing

  Armory 0.92.99.2-testing for Windows XP, Vista, 7, 8+ (32- and 64-bit)
  Armory 0.92.99.2-testing for MacOSX 10.7+ (64bit)
  Armory 0.92.99.2-testing for Ubuntu 12.04+ (32bit)
  Armory 0.92.99.2-testing for Ubuntu 12.04+ (64bit)
  Armory 0.92.99.2-testing for RaspberryPi  (armhf)

  Armory 0.92.99.2-testing Offline Bundle for Ubuntu 12.04 exact (32bit)
  Armory 0.92.99.2-testing Offline Bundle for Ubuntu 12.04 exact (64bit)
  Armory 0.92.99.2-testing Offline Bundle for RaspberryPi  (armhf)

  Armory 0.92.99.2-testing: Signed hashes of all installers

[doug_armory]

It does not mention BIP32 Hierarchical Deterministic Wallets. So it is not supported yet?

Nope. It'll be introduced alongside the 2.0 wallets, which are still in development.

On a different note, can people who have had issues with OS X crashes please give the latest test build (0.92.99.2) a spin? For the life of me, I can't seem to reproduce the crashes that others swear are still present and supposedly OSX-specific. My hunch is that the latest Qt upgrade fixes these crashes. I just can't confirm. Either way, 0.92.99.2 should be a much more pleasant experience for OSX users. Several longstanding bugs have disappeared or been greatly mitigated. There are still a few minor quirks that I'll fix when I can, if I can. (Patching Qt-specific issues can be a nightmare.) As always, feedback is appreciated.

[TimS]

(using 0.92.99.2 now)

Adding a wallet on my supernode instantly shows the balance in the Available Wallets pane and the transactions, as expected (woot woot! The wait almost feels like it's worth it to see that ). However, the balances in the lower right are not immediately updated. I can force them to update by modifying the Filter selected on the lower left. I can email screenshots documenting this if needed to clarify (for privacy reasons, not posting it publicly).

[jammers]

cool, i'll uninstall and delete everything again armory related, and try again, lets see how long it takes from now to build

bitcoin was kept as is, so it loaded up, synced the few blocks quickly, now, quickly scanning through block headers, 50% done in a few minutes

[goatpig]

cool, i'll uninstall and delete everything again armory related, and try again, lets see how long it takes from now to build

bitcoin was kept as is, so it loaded up, synced the few blocks quickly, now, quickly scanning through block headers, 50% done in a few minutes

There are no DB changes in this testing release, there won't be any difference.

[goatpig]

(using 0.92.99.2 now)

Adding a wallet on my supernode instantly shows the balance in the Available Wallets pane and the transactions, as expected (woot woot! The wait almost feels like it's worth it to see that ). However, the balances in the lower right are not immediately updated. I can force them to update by modifying the Filter selected on the lower left. I can email screenshots documenting this if needed to clarify (for privacy reasons, not posting it publicly).

Is the wallet filter set to All Wallets?

[zombieslayer9099]

Is the initial DB build/scan going to be this slow for a while?

I invest in a lot of cloud mining and I need to be able to monitor payments, invest more, etc. with a lot of addresses without having to check each one on blockchain.

[TimS]

(using 0.92.99.2 now)

Adding a wallet on my supernode instantly shows the balance in the Available Wallets pane and the transactions, as expected (woot woot! The wait almost feels like it's worth it to see that ). However, the balances in the lower right are not immediately updated. I can force them to update by modifying the Filter selected on the lower left. I can email screenshots documenting this if needed to clarify (for privacy reasons, not posting it publicly).

Is the wallet filter set to All Wallets?

No, it was set to My Wallets. I have a correction: there's still something wrong, but it's not what I reported at first. Immediately after changing a wallet from Watching-Only to Offline (i.e. specifying that I own it) while My Wallets is selected, the transactions don't appear in the Transactions tab and the balance of that wallet does not show up in the Maximum Funds, etc. balances in the lower right. I can force them to update by modifying the Filter selected on the lower left.
The reverse also occurs: a change from Offline to Watching-Only is not immediately reflected in the transactions/balances.

[goatpig]

(using 0.92.99.2 now)

Adding a wallet on my supernode instantly shows the balance in the Available Wallets pane and the transactions, as expected (woot woot! The wait almost feels like it's worth it to see that ). However, the balances in the lower right are not immediately updated. I can force them to update by modifying the Filter selected on the lower left. I can email screenshots documenting this if needed to clarify (for privacy reasons, not posting it publicly).

Is the wallet filter set to All Wallets?

No, it was set to My Wallets. I have a correction: there's still something wrong, but it's not what I reported at first. Immediately after changing a wallet from Watching-Only to Offline (i.e. specifying that I own it) while My Wallets is selected, the balance of that wallet does not show up in the Maximum Funds, etc. balances in the lower right. I can force them to update by modifying the Filter selected on the lower left.

Oh yeah, I didnt put in a mecanism to update wallet filters from individual wallet status change. Good catch.

[goatpig]

Is the initial DB build/scan going to be this slow for a while?

I invest in a lot of cloud mining and I need to be able to monitor payments, invest more, etc. with a lot of addresses without having to check each one on blockchain.

Fullnode will be slow on HDD until I'm done with the current round of optimizations. Ignore supernode on HDDs. There will be a testing release when the changes are solid. Don't toy with the current version if you don't have a SSD.

[TimS]

Especially important for our more-hardcore users, we now have a "supernode" mode, that doubles Armory's DB size, but indexes all scripts on the blockchain.

My supernode database file is 85.2 GB. This is 2.6x the size of the old Armory DB. Is this size expected? Can someone report the size of the new Armory's fullnode DB size? (I'd imagine it doesn't vary significantly from machine to machine)

85.2 GB - new Armory supernode
32.9 GB - old Armory fullnode
31.5 GB - Bitcoin Core
26.6 GB - raw blockchain