Stuck in mempool- please help me , please

[hosseinimr93]

So it's  completely  marked automatically  now ?? as all is being  flagged RBF, fee bumping though.

Yes, any transaction you make via electrum version 4.4.0 and newer versions are automatically flagged as RBF.
In the older version, it was possible to choose whether you want your transaction to be flagged as RBF or not.

It may worth mentioning that there are nodes that have enabled full RBF and accept the replacement transaction, even if the original one has not been flagged as RBF.
To do this, you need to build the raw transaction and broadcast it using your own node or a tool allowing you to do so.

[Pmalek]

If the node has dropped the original transaction, it will accept the replacement.
If the node still has the original transaction, and has full RBF disabled, it will reject the replacement.
If the node still has the original transaction, and has full RBF enabled, it will accept the replacement, provided the replacement meets the fee criteria for RBF replacements.

Obviously, each node owner can decide for themselves whether or not they will support full RBF. But is there a way for a 3rd-party (like you or me) to know which node supports full RBF? It could help when you need to create such a doublespend transaction.

Even though the purging rate is 10 sat/vByte right now and OP only pays 7, Mempool.Space hasn't dropped his transaction. I am guessing many other nodes still have it in their memory even now. Knowing exactly where to go would speed things up. 

[o_e_l_e_o]

But is there a way for a 3rd-party (like you or me) to know which node supports full RBF? It could help when you need to create such a doublespend transaction.

I'm not aware of any straightforward way to detect whether one of your peers has full RBF enabled or not. The best option if you need to broadcast a full RBF replacement would be to manually connect to well connected nodes which are known to accept full RBF connections (such as https://petertodd.org/2023/why-you-should-run-mempoolfullrbf#full-rbf-peering), or to broadcast via a well connected service which is known to accept full RBF replacements (such as https://mempool.space/tx/push, http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/push).

[Pmalek]

Thanks for the suggestions. Hopefully it can come in handy for those who need it.

The best option is you need to broadcast a full RBF replacement would be to manually connect to well connected nodes which are known to accept full RBF connections (such as https://petertodd.org/2023/why-you-should-run-mempoolfullrbf#full-rbf-peering)

This is for Bitcoin Core and those running their own nodes. Any idea which Electrum nodes one could connect to for similar results?

broadcast via a well connected service which is known to accept full RBF replacements (such as https://mempool.space/tx/push, http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/push).

This is good and anyone could do it who created the transaction. Alternatively, you can get it from a block explorer if it was broadcasted-

[o_e_l_e_o]

This is for Bitcoin Core and those running their own nodes. Any idea which Electrum nodes one could connect to for similar results?

No idea I'm afraid since I don't use third party servers. But if you try to broadcast a full RBF replacement through an Electrum server which does not accept it, it will simply return an error. At that point, you can easily switch to a different server via "Tools" -> "Network" and try again until you find one which accepts your replacement (and then probably check via mempool.space after a few seconds to ensure you got good propagation).