I guess this is only applicable when the transaction has gotten 0 confirmations. This too should have a big risk of getting a stuck transaction usually when there is no transaction with higher fee to replace it and what if the the transaction wasn't marked as replaceable in RBF I guess Reversal will be impossible.
for full-RBF irrespective of been marked as replaceable once there is 0 confirmation i guess it can re replaced with a transaction with higher fee. But what if there are no such transactions for a long time how long will the network congestion last?
It's trivial to do so. Just get a miner to include your desired transaction in their block. Even if its not tagged as RBF, a transaction that is included in a block first is generally final.for full-RBF irrespective of been marked as replaceable once there is 0 confirmation i guess it can re replaced with a transaction with higher fee. But what if there are no such transactions for a long time how long will the network congestion last?
NO, You can immediately undo the transaction, that is the entire idea, the faster the better, you have until the 6th confirmation comes in, if the undo transaction was not issued/seen by the network by that time/block, the undo transaction is no longer valid/accepted and the transaction is permanent.
So the idea is you must submit the undo transaction before the usual/guidance/advise of waiting 6 confirmations before a bitcoin transaction can be considered valid/safe.
Consider the "impossibility"... well some mention a feature which can be used to replace "in flight" transactions, this new idea is to enable "stored/commited transactions" to be "undo"/marked as invalid/undone.
So this would be a change/addition/modification to the bitcoin protocol and source code to *make it possible* =D
The usual advice is to wait 1 confirmation before a Bitcoin transaction can be confirmed. Inclusion of a transaction into a block is generally considered finality and if this is implemented, services who are currently adopting 1-conf transactions will also have to wait for 6 confirmations. So the idea is you must submit the undo transaction before the usual/guidance/advise of waiting 6 confirmations before a bitcoin transaction can be considered valid/safe.
Consider the "impossibility"... well some mention a feature which can be used to replace "in flight" transactions, this new idea is to enable "stored/commited transactions" to be "undo"/marked as invalid/undone.
So this would be a change/addition/modification to the bitcoin protocol and source code to *make it possible* =D
Your advice is trying to solve an issue that has never existed. We cannot expect to babysit people for their carelessness and incompetence. Sent it wrongly? Suck it up. Besides, you've got plenty of great ideas over here; delaying a transactions locally for an hour for you to reflect on it sounds great to me.
