2-month-old transaction still unconfirmed, stuck in mempool

[zabzob]

Thanks guys for all the helpful and instructive posts. I will try the Electrum method soon when I have a little spare time, and report the results. I sent the transaction from the Mycelium wallet, but I think the seed phrase from that wallet should work on Electrum.

Thb though, I'm a bit curious to see how long this transaction will stay unconfirmed in the mempool if I just leave it. Not in a hurry to spend the coins, and having them stuck is a way of bolstering my resolve to hodl

[1714569526]

1714569526

[1714569526]

1714569526

[1714569526]

1714569526

[1714569526]

1714569526

[LoyceV]

I sent the transaction from the Mycelium wallet

This happened to me too once. It's been a while, but I think Mycelium keeps broadcasting the transaction, and after a while gives you the option to drop it. And in my case it also picked it up again after that.
So see if you can drop it, then make a new transaction with higher fee.

having them stuck is a way of bolstering my resolve to hodl

That's working out really well for you given the current Bitcoin price

[zabzob]

I sent the transaction from the Mycelium wallet

This happened to me too once. It's been a while, but I think Mycelium keeps broadcasting the transaction, and after a while gives you the option to drop it. And in my case it also picked it up again after that.
So see if you can drop it, then make a new transaction with higher fee.

I have dropped the transaction on Mycelium countless times, and every time it reappears after an hour or so. This has happened to me on several previous Mycelium transactions, but it has never continued for months like in this case.

having them stuck is a way of bolstering my resolve to hodl

That's working out really well for you given the current Bitcoin price

This stuck transaction is paying for my next coffee   

[LoyceV]

I have dropped the transaction on Mycelium countless times, and every time it reappears after an hour or so. This has happened to me on several previous Mycelium transactions, but it has never continued for months like in this case.

That's why I suggested to make a new transaction (after dropping it). If it uses the same input, the old transaction should be replaced. That's basically the same you'd be doing with Electrum too.

[zabzob]

I have dropped the transaction on Mycelium countless times, and every time it reappears after an hour or so. This has happened to me on several previous Mycelium transactions, but it has never continued for months like in this case.

That's why I suggested to make a new transaction (after dropping it). If it uses the same input, the old transaction should be replaced. That's basically the same you'd be doing with Electrum too.

Oh I see. That would be an easy fix if it works, will try

[hosseinimr93]

but I am not aware of any wallet that has a built in feature to do that

Sparrow allow you to change addresses when replacing a RBF-enabled transaction with a new one paying higher fee.

Thb though, I'm a bit curious to see how long this transaction will stay unconfirmed in the mempool if I just leave it. Not in a hurry to spend the coins, and having them stuck is a way of bolstering my resolve to hodl

Take note that each node has its own mempool.
The fee rate you used for your transaction is lower than the purging fee rate of nodes with default mempool size and many nodes have probably dropped your transaction from their mempool.
Even if your transaction is rebroadcasted, there are nodes that will reject it. So, you should be able to find nodes that don't have your transaction in their mempool.

[Cricktor]

That's only possible when you perform Full RBF it allows the user to change any aspect of the transaction and thus include output addresses too but I am not aware of any wallet that has a built in feature to do that, we have to manually sign in the transaction and then broadcast it but with the conventional RBF aka the RBF we see in wallets like electrum where we can only increase the fees and it doesn't allow changing the output address but if we opt out the cancel (double spending) we can change the output address while paying a higher fee than the original transaction.

Reminder to myself: test RBF more thoroughly with a few different reputable wallets (Core, Electrum, Sparrow, ...) in Testnet.

Personally I didn't have to use RBF or Full RBF so far. I know that Electrum offers to "cancel" an unconfirmed transaction which is then a (Full?) RBF back into your own wallet. Since a few recent versions of Electrum RBF is active per default and not an option anymore. Hm, I have to admit that I didn't look into all details of RBF, time to change it.  

[hosseinimr93]

I know that Electrum offers to "cancel" an unconfirmed transaction which is then a (Full?) RBF back into your own wallet.

The cancel transaction feature has nothing to do with full RBF.
Electrum allow you to replace a transaction that has been flagged as RBF with a new one sending the fund to yourself. You can't do so if the transaction has not been flagged as RBF and that means that there is no full RBF in electrum.

[Cricktor]

...

If Electrum's "cancel" RBF has nothing to do with Full RBF then it's not correct what @Findingnemo said, as far as I understand it, because Electrum's "cancel" RBF transaction spends the same inputs but replaced the outputs completely. As far as I remember Electrum doesn't offer you anymore an option to flag RBF or not, it's on by default in Electrum without option to turn if off, thus any transaction sent from recent Electrum versions should be "cancellable" by RBF in Electrum.

[hosseinimr93]

If Electrum's "cancel" RBF has nothing to do with Full RBF then it's not correct what @Findingnemo said, as far as I understand it, because Electrum's "cancel" RBF transaction spends the same inputs but replaced the outputs completely.

I reread Findingnemo's post and I am not sure I am understanding him correctly. If I am understanding Findingnemo correctly, he says full RBF means changing addresses and that's wrong.

Full RBF is a setting for nodes.
In the case a node has enabled full RBF, it accepts the replacement transaction even if the original one has not been flagged as RBF.