Topic: Bump fee window - page 3. (Read 641 times)

You can follow this guide to manually remove a transaction from your wallet and double-spend it. Keep in mind that most nodes by default will reject a transaction spending the same inputs even if it pays a higher fee. You are more likely to succeed after a few days when most nodes drop the first transaction from their mempools.

So the question is how to delete a transaction in Electrum, so that a new RBF type is sent to a mempul but with a higher Commission so that it is carried out faster than the first, but not as now to the same wallet, but to another one, let's say

Either the transaction had a rbf flag, it wasn't broadcasted succesfully, you waited untill the original transaction was dropped from the mempool of most of the other nodes, the first transaction was invalid or you got extremely lucky to have had it relayed by nodes that were either patched or for any reason didn't have the original tx in their mempools.

The default action for a node when it receives a transaction double spending unspent outputs from an unconfirmed transaction in their mempool without the original tx having an rbf flag is to reject the second (double spending) transaction. This is the case with default node implementations.

Anyways, removing a broadcasted, valid, transaction from your own mempool does not remove it from the mempool of any other node.

The protocol simply does not allow you to remove non-rbf transactions from other node's mempools, simple as that (and for tx's with the rbf flag, you do not remove the original tx either, you simply replace it). So any function from any wallet that says otherwise is simply removing the transaction from your wallet, removes it from your mempool and/or stops broadcasting the transaction. But once a succesfull transaction is broadcasted, it stays broadcasted, and the only thing that'll remove it from other node's mempools is time (a long time) or the presence of the rbf flag in the original tx.

In Bitcoin Core, this was done simply-I delete the transaction from the mempool, and then conduct a new one with a higher Commission, as soon as it passed - the old one will not be held and will be discarded in any case by all nodes

you can remove all transactions from your own mempool by stopping core, deleting the mempool db, and starting your wallet with -zapwallettxes, but that's just from your own mempool. AFAIK, the gui has a feature to "abandon transaction", but that's more or less the same (it differs on a couple things on a deeper level, for example iirc abandoning only works after the tx is no longer in your own mempool so it clears the tx from your wallet not your mempool) . Once a valid transaction has been broadcasted, it'll be stored in the mempool of most of the other nodes of the network, nodes you have no controll over whatsoever.

There is no way of "deleting" a transaction from other node's mempools, the only way it'll get cleared from other node's mempool is if your transaction is included into a valid block, or if the node itself decides to remove the transaction (usually because the mempool is over a certain size, or if the transaction remained unconfirmed for a certain amount of time).

I would discourage to abandon or zap unless you have a very good understanding of what you're doing... Eventough you no longer have a record of an unconfirmed transaction that has been abandoned, it might still be available in the mempool of a mining node, so a miner might still use this transaction in his/her block. You might end up paying somebody twice, or you might end up double spending an unconfirmed output, and the receiver might brand you as a "scammer" as a result (eventough you had no intention to scam)

In the future, I would just like to have this opportunity. For example on Bitcoin Core this is available and you can cancel a transaction that is still hanging in my pool and has not been confirmed

You can't delete a transaction once it's broadcasted (doesn't matter if it has the rbf flag or not). You either wait untill it's confirmed or untill most nodes dropped it from their mempool, or you bump the fee (create a new transaction to replace the previous one, but not deleting it).

Why would you want to delete a broadcasted transaction?

Thank you for your comprehensive answer. How do I delete a transaction at all until it is confirmed and if it is RBF?

it is also possible that some nodes or miners' node reject transactions that are "not final" and could be changed in the future. the option is there to let users have a way of removing the RBF flag from their transactions and make it final so that they don't get stuck.

What have been said by both Omega and HCP is correct.
If you tick the "Final" checkbox, the transaction will be broadcasted without the RBF flag. Therefore, you will not be able to bump the transaction fees if it gets stuck (btw, right now 150 sat/byte is the recommended fee for a fast confirmation).

I can't think of any practical use case for this unless when sending a payment to a service/merchant that accepts transactions with zero confirmation. They usually reject RBF transactions and do not accept the payment unless after 1 confirmation or more.

OmegaStarScream is correct...

Here is my original (unconfirmed) transactions:



Bumping the fee with the "final" box checked, it marks the transaction as "RBF: False":



But if I leave the box empty, it marks the transaction as "RBF: True":

Oк. Let's wait who knows for sure) And another question in which case it may be necessary to set it so as not to raise it any more

I believe (correct me if I'm wrong) it means that your transaction will be marked as "final" and won't be able to bump the fee anymore.

Give this a read (if interested to know how it works): https://www.reddit.com/r/Bitcoin/comments/3uphgv/eli5_what_is_rbfreplacebyfee/

What does setting the Final check mark in this window do?