Quote from: Cricktor on Today at 08:12:36 AM

This doesn't solve the problem as likely a lot of mining pools have their nodes set to Full-RBF policy which allows replacement transactions in any case, even if your transaction flags it's non-replacable.

The only solution is to confirm aka mine the transaction undercover, i.e. without making it publicly visible, like via slipstream.mara.com.

BTW, there's a forum rule which frowns multiple consecutive posts by same user within less than 24h. If you want to post some additional things, you can simply edit your last post when it's the last one in a topic. It's no rocket science...

Ahh ok, I have never needed to make transactions of that type and I know that they exist and little else, but the way I understood it, if that type of attack can be perpetrated, what is the use of RBF? It makes no sense.

On the other hand, having created several posts you are right, I will see if I can correct it, I apologize.