Armory - Discussion Thread

[Portnoy]

Hi,

After doing further research I have discovered that my transaction size was too large for the 0.0001 transaction fee paid. This was a standard transaction fee set by Armory (My bit coin Client) my Transaction size is 9615 (bytes) so that's nearly 10 Kilobytes which means my Fee should have been 10 x the amount I paid.

I am really annoyed that I wasn't automatically prompted to pay this amount when I did the transaction, and now my money is just stuck in the network trying hard to find some miner (or mining pool) that is generous enough to include my cheap transaction instead of other transactions that pay a higher fee per kilobyte.

As such is there anyway to cancel this transaction so that the Bit Coins are returned to my Wallet? I want to be able to re-send this again without double spending, but this time with a higher transaction fee so it will confirm through the network more quickly.

I have been told that it may still confirm but I could be waiting upto 10 days, the merchant cant wait that long to receive his money.
If I had know I would have increased the fee to 0.001 without hesitation... this is really frustrating.

I have been told that there may be a way to remove the transaction from the wallet and the block chain, or Eventually (usually within 2 to 4 days) if the transaction isn't confirmed, it will be dropped from the memory pool of the peers and the coins returned?

I've had this happen with other clients and after 3 days got the coins back.  

[Ilan1]

Hi,

After doing further research I have discovered that my transaction size was too large for the 0.0001 transaction fee paid. This was a standard transaction fee set by Armory (My bit coin Client) my Transaction size is 9615 (bytes) so that's nearly 10 Kilobytes which means my Fee should have been 10 x the amount I paid.

I am really annoyed that I wasn't automatically prompted to pay this amount when I did the transaction, and now my money is just stuck in the network trying hard to find some miner (or mining pool) that is generous enough to include my cheap transaction instead of other transactions that pay a higher fee per kilobyte.

As such is there anyway to cancel this transaction so that the Bit Coins are returned to my Wallet? I want to be able to re-send this again without double spending, but this time with a higher transaction fee so it will confirm through the network more quickly.

I have been told that it may still confirm but I could be waiting upto 10 days, the merchant cant wait that long to receive his money.
If I had know I would have increased the fee to 0.001 without hesitation... this is really frustrating.

I have been told that there may be a way to remove the transaction from the wallet and the block chain, or Eventually (usually within 2 to 4 days) if the transaction isn't confirmed, it will be dropped from the memory pool of the peers and the coins returned?

Okay, so you fell into a dead spot in the fee logic.  We recently discovered a bug that causes Armory to under-calculate the fee for certain kinds of transactions.  This was already discovered and fixed for 0.91-beta (will be releasing a proper testing version of it soon).    This affects a very small number of transactions, but it appears you fell into that crack...

As for resolving it... you could consider using Help->Clear All Unconfirmed, then restart Armory (and Bitcoin-Qt/bitcoind, if running it manually).  Then try re-sending the tx.  If it was an offline tx, you will be able to simply rebroadcast (don't need to recreate and re-sign it).  The success of this operation depends on how many peers you are connected to that still remember it. Once there is a critical mass that have forgotten it (maybe 10-20%), your transaction will go through

Thank you I will give this a try, it was an offline transaction and the signed transaction has a low fee of 0.0001 which is what caused the problem in the first place... If I want to increase this to 0.001, is there anyway of doing this without creating and signing a new transaction? Thanks for your help.

[Ilan1]

Hi,

After doing further research I have discovered that my transaction size was too large for the 0.0001 transaction fee paid. This was a standard transaction fee set by Armory (My bit coin Client) my Transaction size is 9615 (bytes) so that's nearly 10 Kilobytes which means my Fee should have been 10 x the amount I paid.

I am really annoyed that I wasn't automatically prompted to pay this amount when I did the transaction, and now my money is just stuck in the network trying hard to find some miner (or mining pool) that is generous enough to include my cheap transaction instead of other transactions that pay a higher fee per kilobyte.

As such is there anyway to cancel this transaction so that the Bit Coins are returned to my Wallet? I want to be able to re-send this again without double spending, but this time with a higher transaction fee so it will confirm through the network more quickly.

I have been told that it may still confirm but I could be waiting upto 10 days, the merchant cant wait that long to receive his money.
If I had know I would have increased the fee to 0.001 without hesitation... this is really frustrating.

I have been told that there may be a way to remove the transaction from the wallet and the block chain, or Eventually (usually within 2 to 4 days) if the transaction isn't confirmed, it will be dropped from the memory pool of the peers and the coins returned?

I've had this happen with other clients and after 3 days got the coins back.  

Thanks, this is a great relief to know, what happens to the transaction in the block chain, does it just disappear?

[etotheipi]

Thank you I will give this a try, it was an offline transaction and the signed transaction has a low fee of 0.0001 which is what caused the problem in the first place... If I want to increase this to 0.001, is there anyway of doing this without creating and signing a new transaction? Thanks for your help.

Whoops -- I misspoke.  You definitely have to recreate and re-sign, if you're going to increase the fee.  The directions I gave above are given to people whose tx get stuck because of network issues, not fee issues.  In those cases, they just need to rebroadcast -- but you'll definitely need to recreate and re-sign it.

[Ilan1]

Thank you I will give this a try, it was an offline transaction and the signed transaction has a low fee of 0.0001 which is what caused the problem in the first place... If I want to increase this to 0.001, is there anyway of doing this without creating and signing a new transaction? Thanks for your help.

Whoops -- I misspoke.  You definitely have to recreate and re-sign, if you're going to increase the fee.  The directions I gave above are given to people whose tx get stuck because of network issues, not fee issues.  In those cases, they just need to rebroadcast -- but you'll definitely need to recreate and re-sign it.

Thank you, I did already try doing this, but the network thought I was "double spending" and therefore would not add my "new" transaction to the Block Chain, how do I clear the old transaction from the block chain to allow me to create a new one?

[e4xit]

Hi,

Im using Armory 0.9 Beta on OSX, it seems to sync up with the network and stuff OK, but in the bottom right where it either says "disconnected" or "Connected (288888 blocks)" it flashes very quickly between these two messages, like a couple of times per second.

Sometimes it is predominantly 'disconnected' but I can see it flashing, and sometimes it is 'Connected (288888 blocks)' and it flashes...

Anyone else experience this/able to help me troubleshoot this?

Thanks.

This sounds like your bitcoin Qt has reached -maxconnections and won't allow Armory to become max+1. Maybe try launching Armory the instant that Bitcoin client is launched, as it could be that your router is limiting p2p network connections (this will give Armory the best opportunity to be allocated with one of the p2p connection slots)

Even if that's not it, it would be useful to have some mechanism whereby Armory can take priority over other connections, as I've had this problem myself (solved by changing the network environment to allow more p2p connections to bitcoind). Possibly a point for core development, though.

Carlton i think you might have hit the nail on the head here... I have modified my bitcoin.conf to only allow Bitcoin-QT to have 10 connections max, also I am usually letting it sync fully (maxxing out the connections to 10) before starting Armory, so I guess it sounds like what you have experienced...

i do also have a slightly dodgey router though, even though it is supposed to be decent it needs a hard reset once or twice a day which I KNOW is not right but I have tried absolutely everythign to sort that out...

Will try opening Armory quickly after Bitcoin-QT is opened to try and get it in a 'reserved' slot when I get home tonight

[WiiD]

Since i got it work properly, now every ~5 hours my Windows says that Armory does'nt work anymore and it had to be closed. After relaunching, it has to always scan about 2-3 hours for Transaction History. So even if i had my PC turned on the hole day and night, i can't access my BTCs if i need them. There is the Transaction History Scanning for 2-3 hours every time, and then about a hour later, sometimes just 10 minutes, it crashes and anything repeats.

Could you please fix BOTH (Transaction History Scanning everytime) (Armory crashes all time) problems with Armory 0.9.1? When it will be available? Tomorrow? Next week? Next month? I just need a time frame.

[ShadowOfHarbringer]

Hello @etotheipi,

Any plans for BIP38 in Armory anytime soon ?

What is the status of BIP38?  I haven't been following the discussion. 

Well i haven't been following the discussion as well, but for example https://bitcoinpaperwallet.com/ already supports it.

It seems the implementation is not very widespread across Bitcoin clients however.

[marcus_of_augustus]

Hi,

Im using Armory 0.9 Beta on OSX, it seems to sync up with the network and stuff OK, but in the bottom right where it either says "disconnected" or "Connected (288888 blocks)" it flashes very quickly between these two messages, like a couple of times per second.

Sometimes it is predominantly 'disconnected' but I can see it flashing, and sometimes it is 'Connected (288888 blocks)' and it flashes...

Anyone else experience this/able to help me troubleshoot this?

Thanks.

This sounds like your bitcoin Qt has reached -maxconnections and won't allow Armory to become max+1. Maybe try launching Armory the instant that Bitcoin client is launched, as it could be that your router is limiting p2p network connections (this will give Armory the best opportunity to be allocated with one of the p2p connection slots)

Even if that's not it, it would be useful to have some mechanism whereby Armory can take priority over other connections, as I've had this problem myself (solved by changing the network environment to allow more p2p connections to bitcoind). Possibly a point for core development, though.

Carlton i think you might have hit the nail on the head here... I have modified my bitcoin.conf to only allow Bitcoin-QT to have 10 connections max, also I am usually letting it sync fully (maxxing out the connections to 10) before starting Armory, so I guess it sounds like what you have experienced...

i do also have a slightly dodgey router though, even though it is supposed to be decent it needs a hard reset once or twice a day which I KNOW is not right but I have tried absolutely everythign to sort that out...

Will try opening Armory quickly after Bitcoin-QT is opened to try and get it in a 'reserved' slot when I get home tonight

If that is the case you can put a "connect=IP-of-armoury-machine" in bitcoin.conf ... maybe even a "addnode=IP-of-armoury-machine" will suffice, where IP-of-armoury-machine=127.0.0.1 for localhost.

[etotheipi]

Since i got it work properly, now every ~5 hours my Windows says that Armory does'nt work anymore and it had to be closed. After relaunching, it has to always scan about 2-3 hours for Transaction History. So even if i had my PC turned on the hole day and night, i can't access my BTCs if i need them. There is the Transaction History Scanning for 2-3 hours every time, and then about a hour later, sometimes just 10 minutes, it crashes and anything repeats.

Could you please fix BOTH (Transaction History Scanning everytime) (Armory crashes all time) problems with Armory 0.9.1? When it will be available? Tomorrow? Next week? Next month? I just need a time frame.

At the very least, the scanning is fixed in the latest version currently in testing (0.91-beta).  0.90 rescans every time there's a crash, but we determined that was wholly unnecessary.  A couple pages back I posted a testing version you can try.  You'll have to rebuild and rescan the first time, but you shouldn't have any rescanning after that unless you import or sweep private keys. 

Though, that testing version is a still a bit too young for most people.  I think we will have the new version officially out in a couple weeks.

[Carlton Banks]

Even if that's not it, it would be useful to have some mechanism whereby Armory can take priority over other connections, as I've had this problem myself (solved by changing the network environment to allow more p2p connections to bitcoind). Possibly a point for core development, though.

If that is the case you can put a "connect=IP-of-armoury-machine" in bitcoin.conf ... maybe even a "addnode=IP-of-armoury-machine" will suffice, where IP-of-armoury-machine=127.0.0.1 for localhost.

That's a good tip, although in my specific situation I'm not sure what the effect would've been, as I had p2pool connecting to bitcoind on the same machine back when it was an issue (the reason I was limiting -maxconnections). I now have  separate machines to run Armory and p2pool, thankfully.

I'm wondering now whether there's a router on the market with a drivebay, SATA interface and some slightly unnecessary CPU capacity. Would be great for running the household bitcoind node.

[Zoella]

...

At the very least, the scanning is fixed in the latest version currently in testing (0.91-beta).  0.90 rescans every time there's a crash, but we determined that was wholly unnecessary.  A couple pages back I posted a testing version you can try.  You'll have to rebuild and rescan the first time, but you shouldn't have any rescanning after that unless you import or sweep private keys. 

Though, that testing version is a still a bit too young for most people.  I think we will have the new version officially out in a couple weeks.

Is the slowness issue on linux fixed?

https://github.com/etotheipi/BitcoinArmory/issues/171

The wallet just got slower and slower after receiving approximately 2 transactions a day for a month for me. Now it's completely unusable.

Linux test version of 0.91-beta?

[etotheipi]

...

At the very least, the scanning is fixed in the latest version currently in testing (0.91-beta).  0.90 rescans every time there's a crash, but we determined that was wholly unnecessary.  A couple pages back I posted a testing version you can try.  You'll have to rebuild and rescan the first time, but you shouldn't have any rescanning after that unless you import or sweep private keys. 

Though, that testing version is a still a bit too young for most people.  I think we will have the new version officially out in a couple weeks.

Is the slowness issue on linux fixed?

https://github.com/etotheipi/BitcoinArmory/issues/171

The wallet just got slower and slower after receiving approximately 2 transactions a day for a month for me. Now it's completely unusable.

Linux test version of 0.91-beta?

We put in a fix for some of the most serious slowness issues.  There was some inefficiencies in the way it stored and scanned live unconfirmed transactions, that only became apparent when the network volume picked up in recent months.  0.91-beta should have that fixed.

Don't use the testing version yet.  Simply close Armory, go to your ~/.armory directory and delete mempool.bin.  Restart Armory.  mempool.bin will reaccumulate, but it should take a couple days for it to bog down your system again, then simply redo it.  0.91 will have this fixed.

Let me know if that's not it.  (also, how big is your mempool.bin, before you delete it?)

[Zoella]

...

At the very least, the scanning is fixed in the latest version currently in testing (0.91-beta).  0.90 rescans every time there's a crash, but we determined that was wholly unnecessary.  A couple pages back I posted a testing version you can try.  You'll have to rebuild and rescan the first time, but you shouldn't have any rescanning after that unless you import or sweep private keys. 

Though, that testing version is a still a bit too young for most people.  I think we will have the new version officially out in a couple weeks.

Is the slowness issue on linux fixed?

https://github.com/etotheipi/BitcoinArmory/issues/171

The wallet just got slower and slower after receiving approximately 2 transactions a day for a month for me. Now it's completely unusable.

Linux test version of 0.91-beta?

We put in a fix for some of the most serious slowness issues.  There was some inefficiencies in the way it stored and scanned live unconfirmed transactions, that only became apparent when the network volume picked up in recent months.  0.91-beta should have that fixed.

Don't use the testing version yet.  Simply close Armory, go to your ~/.armory directory and delete mempool.bin.  Restart Armory.  mempool.bin will reaccumulate, but it should take a couple days for it to bog down your system again, then simply redo it.  0.91 will have this fixed.

Let me know if that's not it.  (also, how big is your mempool.bin, before you delete it?)

Did a complete reinstall a couple days ago (including rebuilding OS). Imported wallets and synced, but it immediately locked up after first sync. I was never able to access wallet properties or the transaction tab. Just deleted mempool.bin (6.5MB) and starting up again.

[exponential]

Is there anywhere I can see an example of a Wallet being restored from the paper backup?

[milkshoe]

Is there anywhere I can see an example of a Wallet being restored from the paper backup?

Just try it by yourself It's working like a charme!

I cannot imagine to use a better wallet than Armory! But as I wrote here https://bitcointalk.org/index.php?topic=503631.0 I am concerned about usb key security (I am ultra paranoid).

Currently the safest method for transferring unsigned&signed transactions is to type it by hand into the computers, right? Now I am asking myself if I can loose my Bitcoins when I have a typo in my transaction plaintext (which is very likely) or does Armory check the file integrity and I just need to check the transaction details Armory brings up to me.

Or should I better wait for your audio transfer feature? (So awesome!)

[Zoella]

...

At the very least, the scanning is fixed in the latest version currently in testing (0.91-beta).  0.90 rescans every time there's a crash, but we determined that was wholly unnecessary.  A couple pages back I posted a testing version you can try.  You'll have to rebuild and rescan the first time, but you shouldn't have any rescanning after that unless you import or sweep private keys.  

Though, that testing version is a still a bit too young for most people.  I think we will have the new version officially out in a couple weeks.

Is the slowness issue on linux fixed?

https://github.com/etotheipi/BitcoinArmory/issues/171

The wallet just got slower and slower after receiving approximately 2 transactions a day for a month for me. Now it's completely unusable.

Linux test version of 0.91-beta?

We put in a fix for some of the most serious slowness issues.  There was some inefficiencies in the way it stored and scanned live unconfirmed transactions, that only became apparent when the network volume picked up in recent months.  0.91-beta should have that fixed.

Don't use the testing version yet.  Simply close Armory, go to your ~/.armory directory and delete mempool.bin.  Restart Armory.  mempool.bin will reaccumulate, but it should take a couple days for it to bog down your system again, then simply redo it.  0.91 will have this fixed.

Let me know if that's not it.  (also, how big is your mempool.bin, before you delete it?)

Did a complete reinstall a couple days ago (including rebuilding OS). Imported wallets and synced, but it immediately locked up after first sync. I was never able to access wallet properties or the transaction tab. Just deleted mempool.bin (6.5MB) and starting up again.

OK, after restarting sans mempool.bin, the system threw up an error message about syncing. Bottom right corner said connected (false blocks), and a mouse over stated 500+ months behind. Again deleted mempool.bin which had grown to 11MB and restarted. Now showing connected (0 blocks) for the last hour while it synced/built database. Scanning transaction history is now estimated at 60 months and the app has frozen again. The mempool.bin file is currently 455.2kB.

[CircusPeanut]

Is there anywhere I can see an example of a Wallet being restored from the paper backup?

Here is demo that I did for a user:

http://www.youtube.com/watch?v=WTwbc3fJsEg

At minute 29 we get into restoring from a backup.

There is quite a bit of content on this video although it's just an unedited google hangout so the quality is not so great.

I am concerned about usb key security (I am ultra paranoid).

Currently the safest method for transferring unsigned&signed transactions is to type it by hand into the computers, right? Now I am asking myself if I can loose my Bitcoins when I have a typo in my transaction plaintext (which is very likely) or does Armory check the file integrity and I just need to check the transaction details Armory brings up to me.

Or should I better wait for your audio transfer feature? (So awesome!)

The audio transfer feature is 1 or 2 releases away, so you might have to wait a little while.

A USB key is reasonably safe if you only use it for only this purpose on only one online computer.

If you go with manual entry that is the safest although most inconvenient. You do not have to worry about losing your bitcoins. You will have a chance to verify and double check the receiving addresses and amounts before you broadcast your transaction. If you took the time to type it all out, you can take the time to double check the receiving addresses and amounts.

[e4xit]

Hi,

Im using Armory 0.9 Beta on OSX, it seems to sync up with the network and stuff OK, but in the bottom right where it either says "disconnected" or "Connected (288888 blocks)" it flashes very quickly between these two messages, like a couple of times per second.

Sometimes it is predominantly 'disconnected' but I can see it flashing, and sometimes it is 'Connected (288888 blocks)' and it flashes...

Anyone else experience this/able to help me troubleshoot this?

Thanks.

This sounds like your bitcoin Qt has reached -maxconnections and won't allow Armory to become max+1. Maybe try launching Armory the instant that Bitcoin client is launched, as it could be that your router is limiting p2p network connections (this will give Armory the best opportunity to be allocated with one of the p2p connection slots)

Even if that's not it, it would be useful to have some mechanism whereby Armory can take priority over other connections, as I've had this problem myself (solved by changing the network environment to allow more p2p connections to bitcoind). Possibly a point for core development, though.

Carlton i think you might have hit the nail on the head here... I have modified my bitcoin.conf to only allow Bitcoin-QT to have 10 connections max, also I am usually letting it sync fully (maxxing out the connections to 10) before starting Armory, so I guess it sounds like what you have experienced...

i do also have a slightly dodgey router though, even though it is supposed to be decent it needs a hard reset once or twice a day which I KNOW is not right but I have tried absolutely everythign to sort that out...

Will try opening Armory quickly after Bitcoin-QT is opened to try and get it in a 'reserved' slot when I get home tonight

Just to follow this issue up, this worked perfectly for me. The next thing I can think of is to add Armory as a forced connection into the bitcoin.conf file so that I don't have to worry about when I start it up...

If I was going to do this, how would I go about it? What address does Armory connect to QT from? I take it it will look something like:

addnode=127.0.0.1

...but bit of n00b about this stuff. Thanks

[etotheipi]

Just to follow this issue up, this worked perfectly for me. The next thing I can think of is to add Armory as a forced connection into the bitcoin.conf file so that I don't have to worry about when I start it up...

If I was going to do this, how would I go about it? What address does Armory connect to QT from? I take it it will look something like:

addnode=127.0.0.1

...but bit of n00b about this stuff. Thanks

FYI, I'm not positive about this because I'm not that familiar with Tor, but I believe when using Tor, all connections appear to be from 127.0.0.1... so it's not necessarily safe in all  environments.  Someone please correct me if I'm wrong...