[BOUNTY] Help test next major release of Armory! [0.04 BTC/bug]

[etotheipi]

Make some money helping test the new version of Armory (0.89.99-testing)!

Download 0.89.99.14: Windows (32- and 64-bit)
Download 0.89.99.14: Ubuntu/Debian 32-bit
Download 0.89.99.14: Ubuntu/Debian 64-bit
Download 0.89.99.14: Mac/OSX (not very usable in 10.9)



For anyone who's been waiting for the new version of Armory, we're almost there!  But we desperately need more testing.   I tested this bug-bounty idea about a year ago, and it seemed to work pretty well.  Besides bugs, Armory got a ton of polishing, too.  So let's try this again!  If you want to claim a full 0.04 BTC (about $17 USD at the time of writing):

• (1) You must be the first to post the buggy behavior.  If there's an error in the log file, you must copy that error here.
• (2) The bug must be reproducible by me and impact the usability or security in a non-negligible way (things like grammatical error or sub-optimal design choices are welcome, but won't be rewarded with BTC)
• (3) Certain categories of bugs, along with already-known issues are not rewarded (the list is at the end of this post)
• (4) I get the final word in who receives a bounty and how much.  Double-bounties and partial-bounties are possible
• (5) I will cap the payouts to 1 BTC total.  If this is productive, I'll happily increase the limit.  
• (6) You are expected to know how to run and use Armory already.  It's an advanced tool with a bit of a learning curve.  This space is not for teaching you how to use it.  (there's an Armory sub-forum for that).
• (7) Not responsible for lost Bitcoins (though I've never seen even a hint of a problem that would lead to loss of coins).  To use it on testnet, you may have to run Bitcoin-Qt yourself and unselect the first checkbox in the Armory settings window.  Remember that Armory uses "--testnet", Bitcoin-Qt/bitcoind uses "-testnet"

This offer ends at 11:59pm EST, Nov 23, 2013!

The following is a list of new features in Armory.  Yeah, there's a lot!  Please test all aspects of the application, though you might be more likely to find bugs in these new features:

• RAM usage and startup time reduction: RAM reduced to less than 300MB, and startup time typically under 60 seconds after initial DB build!
• Persistent database: Armory now maintains its own blockchain database for fast startup.  Make sure you have space to duplicate the blockchain (will be reduced in a subsequent version; this way was easier for now).
• Full MacOSX support: thanks to picobit for the builder, though the Apple+PyQt bugs prevent full usability in 10.9.  Only accepting bug reports in OSX 10.8.
• New Backup Center:  Better organization and description of backup options.  Includes unencrypted digital backups, now.
• Fragmented Backups:  Shamir's Secret Sharing (M-of-N secret splitting); balance your physical security and redundancy.  Create up to 5-of-6 backups in Standard & Advanced modes.  Up to 8-of-12 in Expert mode.  Fragments are also deterministic for a given M value.  For example, if you make a 3-of-5 backup, you can later make a 3-of-7 and the first 5 will be the same as the 3-of-5
• SecurePrint: Paper backups optionally encrypted with code on screen to prevent private key exposure to printer and other network devices.  SecurePrint code should be identical across all backup types for a given wallet
• Half-sized paper backups:  The chaincode is now derived from the private key, meaning only two lines of data for wallets created with the new version of Armory.  Yet, all backup features work with older wallet without a hitch -- they'll all show four lines (if you don't believe me, prove me wrong and collect your 0.04 BTC!)
• Paper backup tester: test any kind of paper backup before you bury it in your backyard.  Includes subset testing of fragmented backups.
• Message Sign & Verify: Finally Bitcoin-Qt-compatible signing and verification.  Will have a new ASCII-armored version like PGP signing, soon
• Fixed broadcasting non-std signatures:  Older versions of Armory produced signatures that have non-standard padding.  If an older version is used on your offline system, you can't broadcast those signed transactions with 0.88.1 online.  This version will fix the padding and broadcast successfully
• Improve *nix Makefile:  Improved Makefile that should work out of the box on most Linux distros once the proper depedencies are installed.  See the osx_picobit directory for compiling on OSX.

As a reminder, here's some pre-existing features that would benefit from testing:

• Importing & sweeping of private keys.  Single and multi.
• Creating deterministic wallets with customizable unlock time/RAM.
• Restoring paper and digital backups without restarting the app
• Coin control (in Expert usermode)
• Customizable change addresses
• "bitcoin:" URI-handling (with known deficiency on some Linux distros)
• "File" -> "Export Transaction History"
• OFFLINE WALLETS (no offline bundle for this version yet)

Claimed:

whault:  1 x bounty (key calculator not removed)
duxZero:  1 x bounty (tool tips and squashed buttons)
jyyst:  1 x bounty (unicode issues)
simonL: 1 x bounty (corrupt wallet file confusion)
Cyberdyne:  1 x bounty (lingering sys tray icon)
idoB:  1 x bounty (links, grammar and backup fields)
cp1:  2 x bounty (confusing --datadir DNE behavior)
devthedev:  1 x bounty (bad autoscrolling of dashboard)

flipperfish:  1x for the "Send Bitcoins" first five entries bug (I knew about that one... long story)
PRab:  1x for the lots of little issues:  (4 time pwd asking, focus issues, let user choose backup)
greBit:  1x for shutdown hanging (I think this is fixed now, isn't it?)
Zomdifros: 1x for... I don't know what that error is... sending issues... definitely a bug!
elbandi:  1x for UAC issues (will be fixed in 0.91)
tc23emp:  1x for maxConnections error (I've been looking for the src of that bug!  Thanks!)

[etotheipi]

Here's a list of things that are already known that do not qualify for a bounty:

• Yes, Armory requires having the whole blockchain.  Yes, it requires running Bitcoin-Qt in the background.  Yes, sometimes it's difficult to point Armory to the correct bitcoind location.  Yes, Armory now duplicates the blockchain data (will be reduced in the next version...this way was simpler for the overhaul).  Most reports related to general setup will be unrewarded.
• Bugs in online mode must be reported after a full synchronization.  I don't need help finding synchronization/setup bugs (I get plenty of emails).  All bugs assume you are in either in offline mode or fully sync'd in online mode.  
• I know the auto-install bitcoind buttons don't work
• The app initiates a rescan on unclean shutdown.  Yeah, it's kinda slow on mainnet.  Shutdown cleanly as much as possible
• Fee calculations.  Max tx size.  Min tx value.  I know they're outdated.  I will fix them soon.
• The new version is not very usable on OSX 10.9.  I can only accept bugs for 10.8 and lower.  If you run in 10.9,  compare your error messages to this before reporting.  These are actually Apple+PyQt bugs, not mine.
• In some Linux distros/environments, URI-handling is broken.  I can tell you how to fix it if needed.  Should work in Ubuntu+Unity, as well as all Windows verisons.
• WinXP support is hosed.  Goatpig is trying to figure that one out...
• Occasionally the DB gets corrupted and automatically rebuilds.  It takes a while.  And may be inconsistent.  Yeah, it sucks.
• Key Calculator and EC Calculator are both off-limits.  Key calc was meant to be removed, and EC calc is both only for expert users and not very maintained (though it technically works if you have the screen space for it).

I will not be maintaining this list for every reported bug.  You may have to read subsequent posts to find out what's been reported.  Or just post your bug and I'll tell you if I fixed it yet.


Usage notes:

This version maintains a full database between loads.  If you find yourself with incorrect balances or corrupted DB errors, you can use the "Help" menu to reset the DB.  A rescan typically takes about 10-20 min.  A rebuild takes 30-90 minutes followed by the rescan.  I'd like to think this will largely be unnecessary, but it's always useful to someone.

Similarly, you can run with " --rescan" or "--rebuild" on the command line.  Or if you're desperate (or on OSX where CLI options don't work), you can simply "touch ~/.armory/rebuild.txt" or "touch ~/.armory/rescan.txt".  Also "touch ~/.armory/clearmempool.txt" will remove stuck transactions.

[whault]

OSX 10.9, general feeling is that the app is not ready for prime-time. There's a number of crashes that I've encountered, this is the only one I can reliably trigger though.

Print wallet:

Opening "wallet properties" > "backup this wallet" > "create paper backup" will open a standard OSX print window, after about two seconds the window loses focus and will ignore all clicks. Clicking a button before the window loses focus will sometimes cause Armory to crash.


https://i.imgur.com/sVgSxwu.gif

[etotheipi]

OSX 10.9, general feeling is that the app is not ready for prime-time. Almost constant crashes, for which I only know a couple of the triggers.

Can you please run from the terminal and confirm that the printed error messages look like this:

modalSession has been exited prematurely - check for a reentrant call to endModalSession

From the terminal, you can just "cd /Applications; open Armory.app"

[whault]

From the terminal, you can just "cd /Applications; open Armory.app"

You probably want to direct users to run this instead:

Code:

/Applications/Armory.app/Contents/MacOS/Armory

The command you have will execute the app but not print any log output back to the terminal.

Can you please run from the terminal and confirm that the printed error messages look like this:

There's a lot of output like that, mainly when in the wallet properties view.

Code:

2013-11-15 14:18:28.350 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:28.830 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:28.846 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:28.847 Python[22287:507] -[NSApplication runModalSession:]: Use of freed session detected. Do not call runModalSession: after calling endModalSesion:.
2013-11-15 14:18:38.313 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:
2013-11-15 14:18:38.328 Python[22287:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession:

For the crash in the print dialogue:

Code:

/Applications/Armory.app/Contents/MacOS/Armory: line 16: 22555 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py

The full crash log has been DM'd to you.


EC Calculator:

The labels in this view are a little squashed:

https://i.imgur.com/DKIs5MF.png

Clicking the "address book" icon to select a private key hangs the app.

Code:

(ERROR) armoryengine.py:12767 - Waited 20s for addrbook to be returned.  Abort
(ERROR) armoryengine.py:12768 - ID: getTxByHash (86700430)
(ERROR) Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10549, in execAddrBook
    dlg = DlgAddressBook(parent, parent.main, targWidget,  defaultWlt, actionStr, selectExistingOnly, selectMineOnly)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10213, in __init__
    self.setAddrBookTxModel(defaultWltID)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10340, in setAddrBookTxModel
    self.addrBookTxModel = SentToAddrBookModel(wltID, self.main)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armorymodels.py", line 807, in __init__
    for abe in TheBDM.getAddressBook(self.wlt.cppWallet):
TypeError: 'NoneType' object is not iterable

Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10549, in execAddrBook
    dlg = DlgAddressBook(parent, parent.main, targWidget,  defaultWlt, actionStr, selectExistingOnly, selectMineOnly)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10213, in __init__
    self.setAddrBookTxModel(defaultWltID)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 10340, in setAddrBookTxModel
    self.addrBookTxModel = SentToAddrBookModel(wltID, self.main)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armorymodels.py", line 807, in __init__
    for abe in TheBDM.getAddressBook(self.wlt.cppWallet):     
TypeError: 'NoneType' object is not utterable

Sometimes after a crash when doing a full rescan, the app will crash out again with the output:

Code:

-ERROR - 1384487000: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
-ERROR - 1384487000: (StoredBlockObj.cpp:1063) Cannot get tx copy, because don't have full StoredTx!
/Applications/Armory.app/Contents/MacOS/Armory: line 16: 23075 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py

This crash log has been DM'd to you as well.

[etotheipi]

@whault:

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.  

EC & Key Calculators:  Ack!  The Key calculator was meant to be gone, and I normally would've specified that it's off-limits for bug bounties.  But I'll give you a bounty for it, because it is a bug that it's still there!  I need to remove it.

I will update the top post to specify that both key calculator and EC calculator are off-limits for bug bounties, and key calc will be removed.

[whault]

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.

The print issue predates Mavericks, I can replicate it on 10.8 in both the latest stable and the latest beta.

I completely understand your reluctance to support 10.9, it's foreign territory especially as you're not a native developer.

[etotheipi]

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.

The print issue predates Mavericks, I can replicate it on 10.8 in both the latest stable and the latest beta.

I completely understand your reluctance to support 10.9, it's foreign territory especially as you're not a native developer.

Oh, that's right... I do remember having to do some special stuff on OSX with the print dialog.  But I seem to remember that it was fixed with the OSX-specific code... I guess not?

[jl2012]

Is it BIP32 compliant?

[etotheipi]

Is it BIP32 compliant?

Negative.  That's a whole different overhaul, and it would be a total mess to do that overhaul at the same time as this one.

After this release will be a bug-fix and polishing release (like fixing unicode issues, and re-optimizing the database engine).  Then, I'll finish the new wallet format (which is like 75% done already), and that will come with support for BIP 32, compressed public keys, and all the hooks for adding multi-sig. 

[whault]

OSX errors: frustrating I might not be able to claim 10.9 support yet.   I think I have to limit it (and bug bounties) to 10.8.

The print issue predates Mavericks, I can replicate it on 10.8 in both the latest stable and the latest beta.

I completely understand your reluctance to support 10.9, it's foreign territory especially as you're not a native developer.

Oh, that's right... I do remember having to do some special stuff on OSX with the print dialog.  But I seem to remember that it was fixed with the OSX-specific code... I guess not?

Seems not. You can open up the PDF preview and print from there if you are extremely fast (race against the window freezing), but if you manage it Armory will crash and lose it's working database.

[kdrop22]

Looking forward to the new version of the software. What is the tentative release date for the final version.

[SimonL]

Here's a bug I've found since the last stable version, I've tried this on 0.89.99.10-beta and 0.89.99.14-beta and I've done a couple rescans too. It seems for me the transactions tab does not populate until it receives a new block after it has finished loading. It pretty much seems to stay like and looks like it is broken until I left it running for a while and then suddenly all the transactions in the window appears, everything else seems to work fine though. This only seemed to happen the first time it was run so, it might be that everything is catching up the first time and it is taking a really long time to reorganise itself. It does report errors in the log though so here they are.

the log as follows:

Code:

2013-11-15 19:29 (INFO) -- armoryengine.py:12479 - Reading blockchain, pct complete: 0.0
2013-11-15 19:29 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-15 19:29 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-15 19:29 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-15 19:29 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2pD6iHKkB
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 35Fijn44X
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2H5X6XTGs
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: CSFC3QFR
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1907 - Syncing wallet: 2ToSafqhH
2013-11-15 19:29 (INFO) -- ArmoryQt.py:1919 - Current block number: 269713
2013-11-15 19:43 (INFO) -- armoryengine.py:10634 - Received new block.  0000000000000004f6512bbfeccd904fa068123e33d59211253bbd307c54f441
2013-11-15 19:44 (INFO) -- armoryengine.py:10634 - Received new block.  0000000000000004fe7b45f3bbc4c7edbd9ff86c963fe77282453e1b38f66503
2013-11-15 20:12 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-15 20:12 (INFO) -- ArmoryQt.py:4463 - Dashboard switched to fully-online mode
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull1
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3779 - Switching Armory functional mode to "Online"
2013-11-15 20:12 (INFO) -- ArmoryQt.py:3837 - Switching Armory state text to Mgmt:User, State:OnlineFull2
2013-11-15 20:12 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-11-15 20:12 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-11-15 20:12 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (64639402)
2013-11-15 20:12 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ReadBlkUpdate (64639402)
2013-11-15 20:12 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-11-15 20:12 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2013-11-15 20:15 (ERROR) -- armoryengine.py:12372 - Waiting for BDM output that didn't come after 20s.
2013-11-15 20:15 (ERROR) -- armoryengine.py:12373 - BDM state is currently: BlockchainReady
2013-11-15 20:15 (ERROR) -- armoryengine.py:12374 - Called from: armoryengine.py:12563 (35311268)
2013-11-15 20:15 (ERROR) -- armoryengine.py:12375 - BDM currently doing: ReadBlkUpdate (35311268)
2013-11-15 20:15 (ERROR) -- armoryengine.py:12376 - Direct traceback
2013-11-15 20:15 (ERROR) -- armoryengine.py:12378 - Traceback:
Traceback (most recent call last):
  File "/usr/lib/armory/armoryengine.py", line 12368, in waitForOutputIfNecessary
    return self.outputQueue.get(True, self.mtWaitSec)
  File "/usr/lib/python2.7/Queue.py", line 176, in get
    raise Empty
Empty
2013-11-15 20:20 (INFO) -- ArmoryQt.py:4779 - New Block! : 269717
2013-11-15 20:20 (INFO) -- ArmoryQt.py:4803 - Current block number: 269717

And how it looked when the error in the log appeared.

[picobit]

Oh, that's right... I do remember having to do some special stuff on OSX with the print dialog.  But I seem to remember that it was fixed with the OSX-specific code... I guess not?

The print dialog works for me (OS X 10.9) - and at some point it started to work for me in 10.8, too.

[duxZero]

Your (?) tool tips require you to click, hold and drag the mouse off the tool tip to keep it displaying else as soon as you just click it disappears.

--

https://i.imgur.com/TVBGr9M.png

[Mooshire]

I'm on it, Windows 8

[jyyst]

I have got still problem with no ascii, national characters(like ążźć) in label of address.

Code:

(ERROR) Traceback (most recent call last):
  File "/home/piotrek/Apps/BitcoinArmory/qtdialogs.py", line 2198, in acceptNewAddr
    comm = str(self.edtComm.toPlainText())
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)

Traceback (most recent call last):
  File "/home/piotrek/Apps/BitcoinArmory/qtdialogs.py", line 2198, in acceptNewAddr
    comm = str(self.edtComm.toPlainText())
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)

The problem is not new but it still appears so i don't want reward.

[etotheipi]

I have got still problem with no ascii, national characters(like ążźć) in label of address.

Ack, I was just about to add that to the list of off-limit topics.  I'm well aware of Armory's unicode issues, and fixing that is in my plans for the next release after this one.  Since it wasn't on the list, I'll give you the bounty for it.

Your (?) tool tips require you to click, hold and drag the mouse off the tool tip to keep it displaying else as soon as you just click it disappears.

This behaves differently in each OS.  I haven't yet figured out how to make this consistent and friendly.  Still better than the mouse-over-hold-wait-display, which some users didn't figure out.   Again, something else I meant to post as already-known, but I'm not going to be stingy about it.  You tested the interface and found a usability issue.  One bounty for you!

Here's a bug I've found since the last stable version, I've tried this on 0.89.99.10-beta and 0.89.99.14-beta and I've done a couple rescans too. It seems for me the transactions tab does not populate until it receives a new block after it has finished loading. It pretty much seems to stay like and looks like it is broken until I left it running for a while and then suddenly all the transactions in the window appears, everything else seems to work fine though. This only seemed to happen the first time it was run so, it might be that everything is catching up the first time and it is taking a really long time to reorganise itself. It does report errors in the log though so here they are.

Okay, so I haven't heard of this bug in a long time.  I thought it only happened when you have a corrupt wallet in your list.  If you isolate it better, I got a bounty for you!  What OS?  Can you try making a copy of the ARMORY_HOME_DIR (if you have the space for it), then remove the wallets, and run Armory with " --datadir=/new/directory/path".  Create a single new wallet, then restart and let it sync again.  I need to know if it goes away.  If so, then there's an issue with one of the wallets and I'll dig further.

[Mooshire]

Ok, so this isnt a bug, but a suggestion. The percentage complete when downLoading the blocks is really only helpful on the first download. When  i boot up Armory and it says 99% 10 minutes remaining, that doesnt tell me much. Maybe the percentage could be percentage complete since the beginning of the download, or you could include how many blocks behind the client is.

[cp1]

Yes, Armory requires having the whole blockchain.  Yes, it requires running Bitcoin-Qt in the background.  Yes, sometimes it's difficult to point Armory to the correct bitcoind location.

I know this is a known issue, but I'd suggest having a way to enter the satoshi directory in the settings.  When you click the "let armory run bitcoin", Bitcoin home directory could stay editable.  Or change to blockchain directory.