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

[etotheipi]

My apologies guys.  I've been swamped with the new release, and preparing for the conference next week.  I'll spend some time today going through and tallying up how many people get bounties.  If you believe you get a bounty, please PM me your address and let me know if you are okay with a single outgoing payment with all recipients at once.  I prefer to reduce blockchain bloat, but I'm also okay with it if privacy is important to you.

[devthedev]

My apologies guys.  I've been swamped with the new release, and preparing for the conference next week.  I'll spend some time today going through and tallying up how many people get bounties.  If you believe you get a bounty, please PM me your address and let me know if you are okay with a single outgoing payment with all recipients at once.  I prefer to reduce blockchain bloat, but I'm also okay with it if privacy is important to you.

No problem, I was just curious, no rush. PMed

[etotheipi]

I just updated the list on the first post.   I think that covers everything.  I have basically ignored any OSX issues since that was completely hosed.  Hopefully we'll get an OSX build going, after the conference.

If you are on the list, please PM me with payment address and specify if you are okay with me sending one transaction with multiple outputs to everyone receiving a bounty. 

BTW:  a lot of these bugs will actually be fixed in 0.91-beta.  I didn't perceive most of them to be showstoppers for 0.90.  It was the showstopping bugs that I was looking for that would make for an embarrassing release...

Thanks everyone for helping out!  If you continue bug-hunting in 0.90, and find new bugs, feel free to post here and I'll honor the bounty up to the limit I originally specified. 

[devthedev]

I just updated the list on the first post.   I think that covers everything.  I have basically ignored any OSX issues since that was completely hosed.  Hopefully we'll get an OSX build going, after the conference.

If you are on the list, please PM me with payment address and specify if you are okay with me sending one transaction with multiple outputs to everyone receiving a bounty. 

BTW:  a lot of these bugs will actually be fixed in 0.91-beta.  I didn't perceive most of them to be showstoppers for 0.90.  It was the showstopping bugs that I was looking for that would make for an embarrassing release...

Thanks everyone for helping out!  If you continue bug-hunting in 0.90, and find new bugs, feel free to post here and I'll honor the bounty up to the limit I originally specified. 

No problem, I had fun!

[jyyst]

I just updated the list on the first post.   I think that covers everything.  I have basically ignored any OSX issues since that was completely hosed.  Hopefully we'll get an OSX build going, after the conference.

If you are on the list, please PM me with payment address and specify if you are okay with me sending one transaction with multiple outputs to everyone receiving a bounty. 

BTW:  a lot of these bugs will actually be fixed in 0.91-beta.  I didn't perceive most of them to be showstoppers for 0.90.  It was the showstopping bugs that I was looking for that would make for an embarrassing release...

Thanks everyone for helping out!  If you continue bug-hunting in 0.90, and find new bugs, feel free to post here and I'll honor the bounty up to the limit I originally specified. 

It is not a problem for me too. My BTC address: 1Nbu8kh1Y6ti98BazN6KeanYvkUKwvwtd2 . When are you going to fix the error that I reported (crash with a lot of addresses)?

[cverity]

I installed Armory on a Windows 7 work PC with the intention of importing watch-only wallets.

I couldn't get Armory to go into online mode.  Eventually I figured out what was happening.  I log into my PC as a domain user, and my home directory is c:\users\<domain user>.<domain name\ - My USERPROFILE environment variable is set correctly, and bitcoin-qt and bitcoind read from the correct c:\users\<domain user>.<domain name> directory, and my permissions on that directory only give my domain user account access.

I finally discovered, that anytime I launched Armory, the permissions on bitcoin.conf would get changed.  My domain user's permissions would be removed, and replaced by permissions for my local user. As a result, when Armory tried to launch bitcoind in the background, it was unable to read the file and failed to launch.

This only happens when I launch Armory. I does not happen when I run bitcoin-qt or bitcoind independently.

If I tell Armory to not run bitcoin in the background, and I run it myself, then everything worked fine.

However, I did discover a solution. I modified the permissions for bitcoin.conf, by adding my domain user back in with full permissions, and removing permission for the local user to delete the file or modify its permissions.  Armory is now able to go online just fine.

[cverity]

Not so much a bug, but the Transaction Fee tooltip says:

..."for less than $0.01 USD and helps the network"

You might consider rewording this without specifying a USD amount, since with the current USD exchange rate, a .00005 fee is more than $0.01.  Even a relay fee of .00001 is more than $0.01