Bitcoin Forum

Bitcoin => Armory => Topic started by: mrmatt on June 20, 2016, 10:33:24 PM



Title: transactions not broadcasting. Any suggestions?
Post by: mrmatt on June 20, 2016, 10:33:24 PM
Hi, I have mac os.  Installed latest armory and bitcoin core.  But when I try to send a transaction it says it was rejected.

I have everything installed in default locations.

Can anyone give me an idea what to do?

Is there anyone that gives professional support for issues like this?

this is the blockchain.info address where armory says the transaction would appear if it worked:

https://blockchain.info/tx/16637268fd6908d575bae1f0fba2b218219026df90034b71cc13c8656b415a98

Thanks
Matt


Title: Re: transactions not broadcasting. Any suggestions?
Post by: goatpig on June 20, 2016, 10:53:24 PM
rebuild & rescan then try again


Title: Re: transactions not broadcasting. Any suggestions?
Post by: NewBTCGuy on June 27, 2016, 06:52:12 PM
I had the same issue a few months back with both instances of Armory that I was running and couldn't find a solution.  Ultimately I had to copy the Armory private keys into Electrum and then send the bitcoin to other full-node wallets of mine.


Title: Re: transactions not broadcasting. Any suggestions?
Post by: Carlton Banks on June 27, 2016, 07:06:59 PM
The solution is to include sufficient fees in your transaction. Most regular transactions are 0.25 Kb, and current minimum fees (27th June 2016) are around 60-70 satoshis per Kb. (from bitcoinfees.21.co (http://bitcoinfees.21.co))

You can set slightly less than the current price for the minimum, and can expect to wait upwards of 24 hours for the transaction to clear. Setting a little more will be very likely to get your transaction into the chain in less than ~6 blocks, but the situation is not static (big tx rate spikes immediately after could shunt you out of position in line) and the miners don't actually have to mine your transaction, they choose to do it. That means they can choose not to, for whatever reason (or for no reason).


Title: Re: transactions not broadcasting. Any suggestions?
Post by: visdude on June 29, 2016, 02:08:58 AM
The solution is to include sufficient fees in your transaction. Most regular transactions are 0.25 Kb, and current minimum fees (27th June 2016) are around 60-70 satoshis per Kb. (from bitcoinfees.21.co (http://bitcoinfees.21.co))

You can set slightly less than the current price for the minimum, and can expect to wait upwards of 24 hours for the transaction to clear. Setting a little more will be very likely to get your transaction into the chain in less than ~6 blocks, but the situation is not static (big tx rate spikes immediately after could shunt you out of position in line) and the miners don't actually have to mine your transaction, they choose to do it. That means they can choose not to, for whatever reason (or for no reason).
Is there a way to determine the size of the transaction in Armory before finalizing its generation? If not, is that something that can somehow be incorporated into the next release (user-friendly) since transaction fees are critical nowadays for a successful transmission?


Title: Re: transactions not broadcasting. Any suggestions?
Post by: goatpig on June 29, 2016, 03:15:11 AM
Is there a way to determine the size of the transaction in Armory before finalizing its generation? If not, is that something that can somehow be incorporated into the next release (user-friendly) since transaction fees are critical nowadays for a successful transmission?

I'll be adding that at some point in the upcoming release.


Title: Re: transactions not broadcasting. Any suggestions?
Post by: visdude on June 29, 2016, 05:24:51 AM
Is there a way to determine the size of the transaction in Armory before finalizing its generation? If not, is that something that can somehow be incorporated into the next release (user-friendly) since transaction fees are critical nowadays for a successful transmission?


I'll be adding that at some point in the upcoming release.
Cool! That will make transacting a whole lot easier. :)

Thank you, goatpig.