Author

Topic: Can't send via Armory because broadcast times out (Read 300 times)

newbie
Activity: 1
Merit: 0
Hi, I am quite new to Armory. Right now, I use Armory 0.96.0.3 and Bitcoin core 0.14 on Windows 10. A couple of things that happened in the last few days are very confusing to me.

1. It seemed that I was able to send out a transaction a week ago though the change had remained unconfirmed until today when I chose to let Armory 'Clear all unconfirmed'. After restarting Armory, the whole amount of the original transaction seems to have been returned to my wallet including the portion that I thought was successfully sent out a week ago. Does it mean that the recipient did never receive it?

2. Then I tried to send a new transaction. However, Armory failed to execute the Send function and keeps popping out the following message,

The transaction that you just attempted to broadcast has timed out.
The RPC interface of your node is disabled, therefor Aromory cannot use it to gather more information about the timeout. It is recommended that you enable the RPC and try again.

To make things a bit more weirder , I found at 'Troubleshooting Tips for Armory' the following ,

Be aware that Armory connects to Bitcoin Core or bitcoind as a regular peer, not through RPC.

if that's true, why the message i received telling me otherwise. Totally baffled right now. Urgent help and clarification needed. I would really appreciate anyone who is willing to share your knowledge and pull me through this confusion. Thank you very much in advance.

Sincerely yours
Jump to: