zombie coins - an issue with my old unconfirmed transaction #8368

When you check my wallet: https://blockchain.info/address/13XPgmeBu1dFWwXM321L5V3qKDLR7CP3Qd I should own some money but in reality all this bitcoins are locked in never ending unconfirmed transaction. How to deal with this kind of issues in the bitcoin core app? Is there any way to cancel unconfirmed transactions, edit, double spend or mine it by myself, anything that could help me to restore the control of my bitcoins? Is there any expiration time or my zombie coins can hang forever in the network? btw, I created this tx one month ago but receiving time from the network is fresh: https://www.localbitcoinschain.com/tx/33cfd21d6003acb420be90e6692e7bb75b6fc86e54ff0c97dc429afba64645e5 wtf? The bitcoin core automatically rebroadcast it or what?

A fee rate less than minRelayTxFee is usually _(always) rejected by miners on mainnet.

But what exactly it means, your money are lost forever? If you have too much money than instead of burning it you can send it to bitcoin network with 0fee?

No, the transaction likely only exists in your local mempool and the mempools of some block explorers.

You can just send out a double spend with proper fee.

Edit: Make sure the receiver knows that you will double spend the transaction. Also make sure to keep an eye on the fee when you create the double spend with createraw.

but how to make this double spend in the bitcoin core app, is there any tutorial available, command line hack, anything? Whenever I try to make a new transaction I've got an error: "The amount exceeds your balance" :/

Instead of double-spending the tx, wouldn't abandontransaction 33cfd21d6003acb420be90e6692e7bb75b6fc86e54ff0c97dc429afba64645e5 and then restart the wallet make these coins available again?

abandontransaction only works on transactions which are not included in a block and are not currently in the mempool.

@altar13 You could try zapwallettxes.

I think this issue helps to highlight that this could be made far easier for users to resolve. That people keep raising issues for this suggests that a long-term fix (in terms of user experience) still needs to be made. e.g. a GUI interface for zapping txs or double-spending txs - ideally letting the user decide which and the risks behind each option. Is there a "stuck transactions" label or a root cause issue already raised for this?

@rebroad You can help by reviewing #8456, which is a small step towards solving the problem.