..."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
Topic: [BOUNTY] Help test next major release of Armory! [0.04 BTC/bug] (Read 12638 times)
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
..."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
December 04, 2013, 07:04:42 AM
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\.. 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.
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\
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.
December 03, 2013, 03:36:37 AM
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.
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)?
December 02, 2013, 07:07:32 PM
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.
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!
December 02, 2013, 07:05:01 PM
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.
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.
December 02, 2013, 03:52:52 PM
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
December 02, 2013, 01:48:56 PM
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.
December 02, 2013, 11:57:03 AM
Is there any ETA about when the Bounty will be paid out?
November 29, 2013, 06:37:31 AM
I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
I have the exact same issue, running Armory 0.90beta on kubuntu 12.04. When I raise the fee to 0.0001 and wait a few minutes the transaction (list) gets through.
November 27, 2013, 01:04:12 PM
Hi,
I try to run Armory on a lucid x64. It's crashing, here is the stdout and stderr:
stdout: http://pastebin.com/ca9LML95
stderr: http://pastebin.com/EhQ4uapi
i already run bitcoin-qt -rescan, so blockchain sould be good.
What sould i do?
Elbandi
I try to run Armory on a lucid x64. It's crashing, here is the stdout and stderr:
stdout: http://pastebin.com/ca9LML95
stderr: http://pastebin.com/EhQ4uapi
i already run bitcoin-qt -rescan, so blockchain sould be good.
What sould i do?
Elbandi
November 23, 2013, 02:33:23 PM
Code:
2013-11-23 04:33 (ERROR) -- Traceback (most recent call last):
File "qtdialogs.pyc", line 6808, in broadTx
File "ArmoryQt.py", line 2619, in broadcastTransaction
File "armoryengine.pyc", line 10793, in sendTx
ConnectionError: Connection to localhost DNE.
If maxConnections is set in bitcoind, this error shows in the logs after you enter your password to complete sending bitcoins. The GUI doesn't show any error; it just leaves the send window open (password dialog closes itself). Obviously, the bitcoins never send (nothing pending).
Another wierd thing is also happening. While the databases are still being created or transactions are being scanned, the message "You just clicked a bitcoin: link..." pops up when you open armory from the systray. I've never actually clicked on a bitcoin: link, but the program thinks I did. It says to try again when Armory is online. This has never happened when armory is actually online.
Also, not sure if this is the place, but could you consider adding a command-line switch to start armory in the systray (if the systray option is already enabled as well).
November 23, 2013, 11:16:42 AM
Code:
(WARNING) ArmoryQt.py:1391 - Tried to start bitcoind, but satoshi already running
(WARNING) ArmoryQt.py:932 - running from: C:\Users\vbox\BitcoinArmory\ArmoryStandalone\ArmoryQt.exe, key: "C:\Users\vbox\BitcoinArmory\ArmoryStandalone\ArmoryQt.exe" %1
(WARNING) ArmoryQt.py:1013 - app dir: C:\Users\vbox\BitcoinArmory\ArmoryStandalone
(ERROR) armoryengine.pyc:13135 - Resetting BDM and all wallets
Traceback (most recent call last):
File "ArmoryQt.py", line 22, in
File "psutil\__init__.pyc", line 85, in
File "psutil\_psmswindows.pyc", line 15, in
File "_psutil_mswindows.pyc", line 12, in
File "_psutil_mswindows.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.
Unfortunately, the new version doesn't support Windows XP, yet. Goatpig has a solution, but it looks like it would complicate this release (0.90-beta), so it's being reserved for the release after this one (0.91-beta).
November 22, 2013, 07:17:34 PM
Hi,
Latest Armory on windows xp sp3.
I use the windows as normal (regular) user without admin/poweruser permissions (=no write access to c:\windows or c:\program files directory)
i try to start Armory, i got this:
http://imgur.com/tUQNq9n
i think logs and settings should be written to appdata.
Elbandi
Latest Armory on windows xp sp3.
I use the windows as normal (regular) user without admin/poweruser permissions (=no write access to c:\windows or c:\program files directory)
i try to start Armory, i got this:
http://imgur.com/tUQNq9n
i think logs and settings should be written to appdata.
Elbandi
November 22, 2013, 10:04:41 AM
Hi,
Warning - this might be a user error:) - if so, feel free to verbally slap me.
I have downloaded and installed the Armory client. Before committing any funds I wanted to try - Test a Paper Backup. Trouble is, when I press the test backup button, after entering the full root key, nothing happens.
Many thanks & good work on this fantastic client.
Warning - this might be a user error:) - if so, feel free to verbally slap me.
I have downloaded and installed the Armory client. Before committing any funds I wanted to try - Test a Paper Backup. Trouble is, when I press the test backup button, after entering the full root key, nothing happens.
Many thanks & good work on this fantastic client.
Send me a log file. [email protected] . I can usually identify these things pretty quickly!
November 22, 2013, 07:02:42 AM
Hi,
Warning - this might be a user error:) - if so, feel free to verbally slap me.
I have downloaded and installed the Armory client. Before committing any funds I wanted to try - Test a Paper Backup. Trouble is, when I press the test backup button, after entering the full root key, nothing happens.
Many thanks & good work on this fantastic client.
Warning - this might be a user error:) - if so, feel free to verbally slap me.
I have downloaded and installed the Armory client. Before committing any funds I wanted to try - Test a Paper Backup. Trouble is, when I press the test backup button, after entering the full root key, nothing happens.
Many thanks & good work on this fantastic client.
November 21, 2013, 06:32:33 PM
I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
Zomdifros,
Perfect, send me a log file! When you click a button and it doesn't do anything, it's dumping an error message in the log file every time. Usually those are very stupid errors and quick fixes. "File"->"Export Log File" and we'll give you a 1x bounty if there's a real, actionable error in there.
Sure, just sent you an email with the log file!
November 21, 2013, 05:54:03 PM
I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
Zomdifros,
Perfect, send me a log file! When you click a button and it doesn't do anything, it's dumping an error message in the log file every time. Usually those are very stupid errors and quick fixes. "File"->"Export Log File" and we'll give you a 1x bounty if there's a real, actionable error in there.
November 21, 2013, 05:51:39 PM
I had trouble sending a transaction, as the Send! button didn't seem to respond. The first time I got a message my transaction fee was insufficient, yet when I agreed to a higher one .... nothing, no response at all. Cancelling the transaction and trying again didn't work, restarting Armory didn't work.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
However, a minute later it did get trough. This was right after a new block was found. Just a few minutes before this transaction, I sent the same amount (0.1 out of 0.35) to a new address from a previously restored paper wallet, in effect sending it to itself. Only after this transaction got it's first confirmation was I able to send the second one.
November 21, 2013, 01:51:04 AM
Note, the disappearing tx bug has been found! Just posted about it in the other thread. Rapidly getting closer to a releasable piece of software!
November 20, 2013, 03:53:01 PM
Sorry guys, I dropped out of contact for a while to try to get some coding&development done. I will get to all of the posts here eventually. For now, I would just like to post a 0.2 BTC bounty as described in this post. This bug is holding up the release schedule, and I can't reproduce it reliably.
Many of you have reported this occurring at some point. But I still don't have a solid pattern for it. I have a couple things I think might fix it, but I won't know if I've fixed it unless I can reproduce it!
If you have gotten Armory fully online and can do some testing for me, help me find the pattern and claim the 0.2 BTC!
Many of you have reported this occurring at some point. But I still don't have a solid pattern for it. I have a couple things I think might fix it, but I won't know if I've fixed it unless I can reproduce it!
If you have gotten Armory fully online and can do some testing for me, help me find the pattern and claim the 0.2 BTC!
Jump to: