Quote from: ABCbits on Today at 10:06:16 AM

Quote from: Floxynice on Today at 09:30:29 AM

Quote from: ABCbits on January 12, 2025, 08:46:46 AM

Jokes aside, people already can "undo" or "cancel" their unconfirmed transaction thanks to existence of RBF and full-RBF. They just need to use wallet which support such feature, such as Electrum.

My idea of RBF is when your transaction is unconfirmed after a long time of being initiated, maybe miners dropped it because of low transaction fee, you can initiate another transaction with a higher fee to replace the former. If this happens, it means the later transaction is still going to be broadcasted in the network. How then do we replace the former and ensure that the later is also not processed in the network.

Sorry if my question appears amateur. Last week I read about RBF (Replace by Fee) and CPFP (Child Pay for Parent).

If you want to ensure both former (1st) and later (2nd) transaction never confirmed, you justneed to create 3rd transaction using RBF or full-RBF feature.

Thanks, I'll read about full-RBF feature, else I will be tempted to ask how the 3rd transaction will not enter the network.

Quote from: LoyceV on Today at 10:49:52 AM

I like the Linux CLI default of never asking for confirmation. If you're not sure about something, don't tell your computer to do it.

I just imagined a world without noobs where everyone is an expert. There's no room for errors because experts will likely behave like machines. Even experts atimes makes errors or dramatically changes their mind. A 3 second delay could be infinitesimal.