Quote from: Cricktor on September 26, 2024, 11:04:50 AM

Quote from: proenca on September 25, 2024, 10:44:27 PM

What if I found wallet 69, initiated the transaction, and then replaced the transaction myself (by stealing from myself), would it work?
How many times can a transaction be "stolen" before it is mined?

You apparently don't quite understand how RBF and Full-RBF work. As RBF is in the interest of miners/mining pools because it increases the transaction fee, you can safely assume that basically every miner/mining pool has Full-RBF enabled. Therefore you can't prevent RBF even when you flag your transaction as non-RBF.

Didn't you read at least past few pages? Your only chance would be to queue your transaction to be mined non-publicly, e.g. via https://slipstream.mara.com. I searched this thread and below citation is the first hit of it here (page 51 of this thread, so not too far in the past). I took the liberty to shrink the picture in the quoted snippet a bit.

Quote from: Akito S. M. Hosana on August 04, 2024, 07:52:31 AM

The only way to do that is by using the MARA Pool Slipstream. The transaction will be mined before the public key enters the mempool.

It won't actually be seen at all through the mempool.

https://i.postimg.cc/pTmPGBWN/2024-08-04-10-01.png

Thank you. It really works. I tested it by creating a "fragile 69bit" wallet with $50 and made the transfer and the public key was not listed in the mempool.
Now I can continue my code using FPGA. Thank you very much for your kindness.