Clear "stuck" transactions

[jimbursch]

Last week I created a 0.191 btc transaction with 0 tx fee -- moving btc from one wallet to another -- and the transaction never posted to the blockchain -- 0 confirms.

Today I downloaded and installed version .9, and I was looking through the menu options and a saw "Clear All Unconfirmed", so I clicked on it and got the message that unconfirmed messages would be cleared and I can retry "stuck" transactions.

My understanding is that the transaction would have been posted to the bitcoin network and gone into some miners queue to eventually be added to the blockchain, and that because of the 0 tx fee, it may take some time (as long as five days, from what I could ascertain from the forums).

Here are my questions, stemming from my imperfect knowledge of the bitcoin protocol and operation of wallets:

What is a "stuck" transaction and how does a transaction get "stuck"?

Where is a transaction "stuck"? In the wallet? Does a "stuck" transaction get transmitted to the bitcoin network?

Is it possible that my 0.191 transaction is still sitting in miners queue, and may yet get added to the blockchain (it is more than seven days now)?

When I cleared unconfirmed transactions (the 0.191 transaction was cleared), does that mean than the unconfirmed transaction is cleared also from the bitcoin network (cleared from miners queue)?

[1714912597]

1714912597

[1714912597]

1714912597

[1714912597]

1714912597

[jimbursch]

I found the answer to most of my questions here:

https://bitcoinarmory.com/download/troubleshooting/

My only remaining questions is:

When I cleared unconfirmed transactions (the 0.191 transaction was cleared), does that mean than the unconfirmed transaction is cleared also from the bitcoin network (cleared from miners queue)?

When I searched for the tx id on blockchain.info a few days ago, I got no results, which I take to mean that the transaction never got broadcast, nor did the transaction get subsequently broadcast on restarts of Armory. From what I can gather, this sounds like an issue between Armory and QT.

Perhaps I'll try the exact same transaction again and see what happens.

Thanks!

[etotheipi]

Yes, just try it again.  The reason it gets stuck like that is because Armory and Bitcoin-Qt/bitcoind both think it's been broadcast but it actually hasn't been.  You have to use "Help"->"Clear All Unconfirmed" and restart both apps in order to forget about it locally.

After that, just broadcast it again.  It's as if the first one never happened... because it didn...