Segwit Transaction Stucked for a Month - Amazing eh?

[miguelmorales85]

Hi there, I did my first SegWit transaction and due to a mistake and a not so clear GUI in Bitcoin Core I have a transaction stucked for a month.

I wonder if someone can explain how can this happen. In the past I've had low fees transaction stucked for about 3 days to one week, nothing uncommon I dont complain but this is outrageous.

https://blockchain.info/tx/2d73dfb6b98f4dcd066134081a670cda09304b268f0a5d7ca451ed8ed6e7d940


Peace

[1714768046]

1714768046

[1714768046]

1714768046

[1714768046]

1714768046

[cellard]

Hi there, I did my first SegWit transaction and due to a mistake and a not so clear GUI in Bitcoin Core I have a transaction stucked for a month.

I wonder if someone can explain how can this happen. In the past I've had low fees transaction stucked for about 3 days to one week, nothing uncommon I dont complain but this is outrageous.

https://blockchain.info/tx/2d73dfb6b98f4dcd066134081a670cda09304b268f0a5d7ca451ed8ed6e7d940


Peace

Interesting...i've never seen a transaction stuck for months, usually it comes back automatically after a couple of days. What was your mistake exactly?

Im not sure if the fee is too low or not. Segwit transactions are supposed to go with lower fees. But since there is no GUI support yet, the fee is not calculated (I guess you used the command line).

Try -zapwalletttxes to get the money back into your wallet.

[Bitfort]

Meh, this one of the smallest fee i've ever seen (0.544 sat/B ... the normal fee should be above 100 sat/B )

Transaction is not dropped when is being rebroadcasted again (e.g. everytime you open the sending wallet it most probably broatcast it again) ... you would need to keep the wallet offline (not open it)  for few days I think.... but depends on wallet.
I'm almost positive it will never get confirmed ... maybe after years  

[cpfreeplz]

Lol why would you try and send half of a satoshi per byte? Clearly it wasn't ever going to work even with segwit. Maybe 20x that and you'd have a shot at getting confirmed. Yeah you need to figure out how to stop having this tx rebroadcast so it'll pop back in your address.

[HCP]

With Bitcoin Core... you'll want to try this:

• Start Bitcoin Core with the command-line option -walletbroadcast=0. On Linux, you might be able to just run bitcoin-qt -walletbroadcast=0, depending on how your current startup script works. On Windows: find the shortcut for Bitcoin Core on your desktop or start menu; right click it and choose "properties"; add -walletbroadcast=0 to the end of "target", so for example "C:\Program Files\Bitcoin\bitcoin-qt.exe" would become "C:\Program Files\Bitcoin\bitcoin-qt.exe" -walletbroadcast=0; click "Apply"; use that specific shortcut to start Bitcoin Core.
  
• On the Transactions tab, right click the stuck transaction and choose "abandon transaction". Warning: Even though the transaction is listed as abandoned, it can still go through. People have in the past lost money by abandoning a transaction, resending a separate replacement transaction, and then having both transactions go through. The following steps are designed to replace the abandoned transaction in a way which will prevent this sort of double payment from happening.

If "abandon transaction" doesn't work... you can always try -zapwallettxes... That will definitely remove it from your wallet and stop the transaction from being rebroadcast.

Note that these commands are likely to result in wallet rescanning which could involve a lot of time.

[BitNoLimit]

Fees   $ 0.12 only used

you have to take care that mate, at least you had to use couple of bucks

[miguelmorales85]

... What was your mistake exactly?

Im not sure if the fee is too low or not. Segwit transactions are supposed to go with lower fees. But since there is no GUI support yet, the fee is not calculated (I guess you used the command line).

Try -zapwalletttxes to get the money back into your wallet.

I used the GUI. My mistake was to check the option Pay only the required fee of XXXX and then the amount was like 580 satochis, I thought "this is a nice amount per sat" but turns out this was the total fee amount. So that was my mistake, I misunderstood the message.

I understand the command -zapwalletttxes is to remove all wallet transactions that are not in the blockchain


I would like the optional RBF checkbox to be checked by default. That would be useful.

oh and FWIW I went on holidays 3 weeks and turned my node (where the wallet is) off the whole 3 weeks, I returned and still there unconfirmed in the mempool...

Im running my node on linux, I will try abandon transaction with broadcastwallet=0 and let you know the results.

thanks for the recommendations.

[miguelmorales85]

Hello all,

With Bitcoin Core... you'll want to try this:

• Start Bitcoin Core with the command-line option -walletbroadcast=0. On Linux, you might be able to just run bitcoin-qt -walletbroadcast=0, depending on how your current startup script works. On Windows: find the shortcut for Bitcoin Core on your desktop or start menu; right click it and choose "properties"; add -walletbroadcast=0 to the end of "target", so for example "C:\Program Files\Bitcoin\bitcoin-qt.exe" would become "C:\Program Files\Bitcoin\bitcoin-qt.exe" -walletbroadcast=0; click "Apply"; use that specific shortcut to start Bitcoin Core.
  
• On the Transactions tab, right click the stuck transaction and choose "abandon transaction". Warning: Even though the transaction is listed as abandoned, it can still go through. People have in the past lost money by abandoning a transaction, resending a separate replacement transaction, and then having both transactions go through. The following steps are designed to replace the abandoned transaction in a way which will prevent this sort of double payment from happening.

Using on linux

Code:

bitcoin-qt -walletbroadcast=0

and then right click on the TX and selecting "Abandon transaction" WORKED!

Thanks for the info.

Regards,