Topic: Armory 0.93 testing release! (with 0.05 BTC bug bounty) - page 11. (Read 35724 times)

That's a simple UI signaling miss, easy fix.

As for Armory's maintenance routine: the backend polls the blkxxxxx.dat files to detect new blocks. The part of the UI you are looking at (the dashboard) is updated through both reactor signals (polling the socket to the local Core instance, from the Python side) and backend signals. The state you are observing with the disconnected message in the bottom right corner is reactor failing to maintain the socket to Core. However the backend maintenance thread is still running and doesn't care for the socket's state.

In this situation, the dashboard will report you as disconnected, and you won't get ZC transactions in the ledger, but any new transaction with at least 1 confirmation will be properly displayed in the ledger, since the backend maintenance thread is still doing its job.

The simplest way I found to avoid this state is to add addnode=127.0.0.1 to your bitcoin.conf to guarantee Core will reserve a socket for your local instance of Armory.

The Goto button is cut off a little. (Windows 7)

The main header says that Armory is disconnected, the status bar says that it is connected.
According to Bitcoin Core, the current block is 342339 (matching Armory) and Armory is not one of the peers connected to it (Bitcoin Core is at the max connections, so I get why Armory isn't connected currently).
It appears that Armory is not connected, but is still keeping up to date somehow...by reading the blocks from disk, maybe? It's odd that the messages don't seem to match. Is this a bug?
Edit: Since posting, Bitcoin Core has received block 342340, and now Armory says "Disconnected" in the status bar.
Edit 2: Now at block 342348, and Armory shows up like my image above ("Armory is disconnected" and "Connected (342348 blocks)").

Also, the "br>" is still visible.

Actually, it doesn't need to say that in any mode anymore. I'll nuke that dialog.

Indeed it is, which made me find a new bug: On importing a lockbox, I get the following message:

I'm running a supernode, so it doesn't actually need to rescan anything.

1. Yes, vanitygen script address
2. It does this on all incoming transactions, except for those which have inputs from my wallets/lockboxes.

Also Armory keeps saying in a dialog box 'The scanning process halted unexpectedly' or something like that. I tried rebuilding but it said that again. I'm on my 2nd rebuild and rescan.

I'm not sure what you mean by 1. 1-of-1 multisig address? That would be a simple P2PKH. 1-of-N? You would still need the N addresses to either fund the multisig script or redeem the P2SH script. What you have is probably a P2SH address (starts with 3?). What are the underlying addresses? You would have to import their respective private keys to your wallets and create a lockbox from that.


Addresses starting with 3 are P2SH. Does it do it on addresses starting with 1?



This isn't a technical issue, it's more of a feature. You can spend unconfirmed change, that's all. If you want the ability to spend any unconfirmed tx, start a thread, get some users behind the demand, that should get etotheipi's attention.


Lockboxes have backup strings, you're supposed to save that. If you don't have the backup string, you'll have to find the addresses you used for it. The address book dialog used in lockbox creation only displays addresses in use. If you built your lockbox from unused addresses you'll have to go fish for them in each respective wallets properties window (uncheck hide unused) and copy paste the public keys (not the addresses) manually during lockbox creation.


That's part of the new wallets


Same code is used for address and lockbox ledgers, they don't have the same free space as the main ledger.

I have one more small request. Can the minimum required addresses for lockbox creation be lowered to 1? I've got a multisig address that i generated in vanitygen and I can't use it. I don't know how to create it through Bitcoin Qt either

I love armory!

It's perfect other than ongoing issues.

Shortcut command line args get deleted during installation. Auto run is default and can mess me up.

Can't spend unconfirmed transactions.

How do I recreate a lockbox I lost? When creating I can't choose the specific address needed.

Any plans for hd lockbox?

Possibly lockbox transactions mentioned in main screen.

When opening the lockbox screen, it cuts off the top of the window, resizing pops it back down thankfully.

Might as well make the goto button stay open now that it's moved, no need for hiding.

Unfortunately, there's no ideal solution for the Qt dialogs. The Qt dialogs require you to either copy the files over to your normal drive or create a symbolic link to the thumb drive, which will let you access the thumb drive. The native dialogs can pick them up but some people have issues getting the dialogs to work.

Just found something else, when I delete private keys from a wallet (make it watching-only) Armory scans the wallet TX history again.

Also I think it should be changed to where you can go into wallet properties while it is scanning, but not be able to look at balances or send bitcoins, instead next to the addresses put 'Scanning: [percent]% or just the 3 dots that are there when building DB or rescanning it.

One more thing, it seems that the Qt dialog on OSX cannot detect USB drives.

The only bug I can find in .6 is when I click View Details after right clicking a TX, Armory still displays transaction inputs on all incoming transactions only as Non-Standard: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy when that is never the case. All outgoing transactions and any incoming transactions that have inputs from my wallets or lockboxes display normally, and it does this on my Ubuntu VM as well. This isn't a major issue but it does bother me a lot.

Speaking of .6....

As always, use the secure downloader as your primary source!

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

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

  Armory 0.92.99.6-testing: Signed hashes of all installers


The biggest fix is the tx history export.  There were a few things wrong with it that should be fixed now.  

That should be fixed in upcoming .6


That would be kind of a pain. A much cheaper alternative would be freezing armoryd (the save way ArmoryQt.py turned into an exe with its Python environment on Windows).

(Windows 7, 0.92.99.5) When I try to import a lockbox from a file and select a file, the open file dialog quickly closes and reopens. If I select a file from this reopened dialog, it works correctly (puts the second file's content into the window so that I can import it).

When the user has over 100 (or whatever) transactions in the given list, show a search button (e.g. magnifying glass or calendar icon, or just "Search" or "Filter") on the Date column header (or hovering where the "#" is now) of the transaction tableview. Clicking it opens up the dialog that currently opens when you click "Date:" in the hovering box. Maybe add a time option, too.

I don't think that most users would need/want to search by Block # (especially since the Block is not shown on the transaction list!) or need a shortcut to jump to the Top (they have a scroll bar), like the dialog has now. And if you only have a few transactions in your list, there's no point in having anything more complicated than scrolling to search it. Putting the search icon in the Date column header means that you don't have to worry about making space for it, or having it cover data.

Maybe the 100 figure should be configurable, including "always show" and "never show [the search button]" options, to help users discover it and adjust the behavior to their liking? I don't see any other configuration options being necessary.

--supernode, --datadir, and --satoshi-datadir are, to the best of my knowledge, command-line-only options: you can't specify them in a config file (probably others, but those are the ones I've used and noticed it on). This is an annoyance, albeit minor: keeping track of proper shortcuts/startup links to Armory, making sure I don't accidentally let the installer run Armory after it finishes (because it won't specify my command-line options), etc.

Using my supernode to its fullest extent (e.g. running a blockchain explorer) without great difficulty requires running armoryd.py on Linux. It would be nice if Armory (Qt) on Windows could be configured to respond to the same API commands.

TBH, I probably wouldn't be complaining except that you asked for it.

I would say Windows since this is what I dev on 95% of the time. However, I do test the finalized code on Debian and go through the bug checklist initially identified on Windows during the development phase. I don't directly test other Linux distros nor OSX.


Yes, comments and labels are saved within the relevant wallet file.

Armory is most stable on Linux, correct? I have an Ubuntu VM and am testing Armory on it(with blockchain), and I might migrate all my wallets over to that VM since it appears more stable (It can handle Bitcoin Qt on its own).

Also if moving wallet files, are address labels and imported addresses carried over with it?

One caveat: the extent of my testing has been:

• Does it compile?
• Will it load and show my balance

Other than generating a few new deposit addresses, I haven't used it for anything beyond that.

That being said, I'm extremely happy with the improvements in blockchain scanning and load times and haven't noticed any unfixed regressions.

Question to the folks who've been testing 0.93 the most:  what are your biggest remaining concerns with this release?  If I told you I was going to release the software after fixing the tx export problem (which will be in a .6 release in the next 24 hours), what would you complain about the most?  No version of Armory is perfect, and at some point we have to say "pencils down", as long as there's no security or major usability issues.

I'm welcome to take feedback from anyone, but in particular I'm inviting:

helgabutters, TimS, zombieslayer9099, justusranvier, bitpop, and Carlton Banks 

My apologies if you have been participating actively and I missed your name:  I haven't been following this thread too closely myself, and I just picked out names at a glance that had multiple feedback posts.  Ideally, I'd at least get a few thoughts back from everyone who has been involved in this the last few weeks.

(EDIT:  OSX doesn't count... I'm hoping OSX is relatively stable, but at this point we can't dump too much more in terms of resources into it for the 0.93 release)

Even better now: http://www.visualstudio.com/en-us/products/visual-studio-community-vs
Basically, VS Pro is free unless you're a big (>$1m/year) business.