Topic: Armory - Discussion Thread - page 67. (Read 521749 times)

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

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.

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

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

However, the new wallet files will have a much more flexible design that will make it easy to add new encryption and key-stretching methods, etc (including all the other goodies, like multisig, P2SH, compressed keys, etc).  If BIP38 becomes well-supported, I'll happily add it to the list of supported key-encodings in the new wallet files (or can be added even after the wallet files are done)

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

Hello @etotheipi,

Any plans for BIP38 in Armory anytime soon ?

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?

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.

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.

Yes you can change it. Somewhere under settings or tools. You may have to go to expert mode.

Hi, I made a transaction for 2 BTC this morning and it has still not confirmed, the blockchain says "Estimated Confirmation Time Within 6 Blocks (Medium Priority) and then there is a Confirmation Warning message to say "The Transaction Fee is Less than Recommended"

I did not set the transaction fee 0.0001 BTC it was automatically set when I broadcasted the transaction via Armory.

1) How long will I have to wait for the confirmations to show?
2) Can I manually change the transaction fee for future payments through the Armory client?

Thanks

Currently using 0.90-beta. I will most likely stay with this version for the foreseeable as it does literally everything I need it to do.

Will be tipping you some point soon!

Thanks again.

Hey, are you talking about the testing version posted 2 weeks ago (0.90.99)?   Or the 0.90-beta on the website?  Either way, glad to hear some positive feedback, just wanted to get clarity on it.

Fantastic work on 0.90... Not had a single problem with it, it's been brilliant. Wouldn't trust BTC to anything else anymore.

Good question, I haven't tried it!  My guess is:  yes, but the interface may not be all that useful, probably "[Non-standard address]" instead of the address string you're expecting.  That's something I'll have to investigate... (feel free to try it and tell me what happens)

If I create a transaction (on armory version >= 0.91) to spend coins to a P2SH address, will an offline v0.90 armory installation be able to sign it?

Thank you. Nice and "user easy" way of detecting multiple instances

Fixed my problem, explained it here: https://bitcointalk.org/index.php?topic=495487.new#new

This should work with 0.91. Key feature is "enabling P2SH addresses".

Don't know if this the right place to ask, but "Does Armory not support multisig addresses to send BTC to?"

When I try to send BTC this address (which is a multisig address): 39wbuEjp3mfFAB3bTjmkFB69XAmKYRMq5i ,then I get error "You have entered one invalid address..." and after that "Address1 is for the wrong network..."
Armory is version 0.90-beta on 64bit Kubuntu12.04