Good thing, but also writes an error
Might be an issue with how coinb.in calculate fees/byte. Could you paste the raw TX here? 
Topic: Bump fee window - page 2. (Read 652 times)
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
if the original transaction is marked as replaceable (this is the default behaviour in electrum) then simply right clicking it and choosing increase fee, choosing a higher fee and then clicking ok and then sign and broadcast in the next window should do the trick.
Is your replacement transaction having a larger fee per byte than your first transaction?
Yes, twice (x2)Just a web utility tool for you to submit transactions to the network[1].
[1] coinb.in/#broadcast
[1] coinb.in/#broadcast
Good thing, but also writes an error
Perhaps something has changed then, after all, before without problems you do double spending with a higher Commission and before the first is held and the first is discarded. Truth so was on Bitcoin Core wallet, on Electrum here is only until try to understand as to remove from applications transaction to anew broadcast another already suppose
I have updated my reply with more accurate information. Now, it should reflect what you were talking about.
Edit: If the initial transaction is marked as replaceable, its inputs can be spent once again to different outputs if the transaction is forgot by your Bitcoin Core wallet (it can be done manually). The built-in "Bump fee" functionality forces users to decrease the change output's value and does not allow to modify other outputs. If the initial transaction is not marked as replaceable then most nodes will reject another transaction as a double-spend attempt.
For some reason, on the second wallet that acts as a co-signatory for me - after executing the command, the transaction is not deleted, writes unknown see photo
And when try to send a new transaction, this error occurs-see the photo
It's RBF. Is your replacement transaction having a larger fee per byte than your first transaction?And when try to send a new transaction, this error occurs-see the photo
What is this tool? how do I use it? The transaction is ready and signed by all cosigners, it remains to send out
Just a web utility tool for you to submit transactions to the network[1].[1] coinb.in/#broadcast
broadcast using a broadcast tool.
What is this tool? how do I use it? The transaction is ready and signed by all cosigners, it remains to send out
Didn't you finish the article? It also says in black and white to avoid this you need to upload the corrected transaction to a new clean wallet so that this does not happen
Ah well, thought you wanted to put all the steps in the post. Also, you don't need to create a dummy wallet for this, just go online and broadcast using a broadcast tool.After executing this command, nothing happened
TXID has to be in a quotation. For example:Code:
>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>>
Code:
wallet.remove_transaction('1ff95e3c5fced8284f91598583e109a614996f4c1f0ce072631a6611b71d14fe')
After executing the command, you can proceed to spend the funds again in the send tab.
For some reason, on the second wallet that acts as a co-signatory for me - after executing the command, the transaction is not deleted, writes unknown see photo
And when try to send a new transaction, this error occurs-see the photo
Didn't you finish the article? It also says in black and white to avoid this you need to upload the corrected transaction to a new clean wallet so that this does not happen
Ah well, thought you wanted to put all the steps in the post. Also, you don't need to create a dummy wallet for this, just go online and broadcast using a broadcast tool.After executing this command, nothing happened
TXID has to be in a quotation. For example:Code:
>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>>
Code:
wallet.remove_transaction('1ff95e3c5fced8284f91598583e109a614996f4c1f0ce072631a6611b71d14fe')
After executing the command, you can proceed to spend the funds again in the send tab.
Didn't you finish the article? It also says in black and white to avoid this you need to upload the corrected transaction to a new clean wallet so that this does not happen
Ah well, thought you wanted to put all the steps in the post. Also, you don't need to create a dummy wallet for this, just go online and broadcast using a broadcast tool.After executing this command, nothing happened
TXID has to be in a quotation. For example:Code:
>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>>
Code:
wallet.remove_transaction('1ff95e3c5fced8284f91598583e109a614996f4c1f0ce072631a6611b71d14fe')
After executing the command, you can proceed to spend the funds again in the send tab.
If you want to remove any transactions, use the following command in your console.
Code:
wallet.remove_transaction(txid_here)
After executing this command, nothing happened
Code:
>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>>
I really don't recommend anyone doing this. The transaction would re-appear after connecting to the internet and the client starts to synchronize from the Electrum server that it is connected to.
Didn't you finish the article? It also says in black and white to avoid this you need to upload the corrected transaction to a new clean wallet so that this does not happen
in step:
Press CTRL-F on the keyboard, and search for this hash in the file. It should appear 4 times, in different places, you need to delete them, but carefully to keep the JSON syntax intact, so I have highlighted what you need to delete, it should be different for you, but you will get the idea, it should be everything that is highlighted:
does not find the cache for some reason, see photo
Electrum 4.0.2 for Windows
I really don't recommend anyone doing this. The transaction would re-appear after connecting to the internet and the client starts to synchronize from the Electrum server that it is connected to.Press CTRL-F on the keyboard, and search for this hash in the file. It should appear 4 times, in different places, you need to delete them, but carefully to keep the JSON syntax intact, so I have highlighted what you need to delete, it should be different for you, but you will get the idea, it should be everything that is highlighted:
does not find the cache for some reason, see photo
Electrum 4.0.2 for Windows
If you want to remove any transactions, use the following command in your console.
Code:
wallet.remove_transaction(txid_here)
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.
in step:
Press CTRL-F on the keyboard, and search for this hash in the file. It should appear 4 times, in different places, you need to delete them, but carefully to keep the JSON syntax intact, so I have highlighted what you need to delete, it should be different for you, but you will get the idea, it should be everything that is highlighted:
does not find the cache for some reason, see photo
Electrum 4.0.2 for Windows
Have there been any changes in this regard with the time of Bitcoin Core 0.16? Then it was done well and all OK nodes accepted the second transaction with a higher Commission first, and the old one was forgotten later and discarded
However, just as I described above, if you create another transaction spending the same inputs but with completely different outputs then most nodes by default will reject such transaction.Perhaps something has changed then, after all, before without problems you do double spending with a higher Commission and before the first is held and the first is discarded. Truth so was on Bitcoin Core wallet, on Electrum here is only until try to understand as to remove from applications transaction to anew broadcast another already suppose
Have there been any changes in this regard with the time of Bitcoin Core 0.16? Then it was done well and all OK nodes accepted the second transaction with a higher Commission first, and the old one was forgotten later and discarded
No... RBF was rolled into Bitcoin Core in v0.12... which was released in February 2016. That's a full 2 years BEFORE v0.16 (Feb 2018).
The thing is that RBF was, and still is, Opt-In. You have to specify that you want your transaction to be RBF:
You can set it to default to this by using walletrbf=1 in your bitcoin.conf file
Have there been any changes in this regard with the time of Bitcoin Core 0.16? Then it was done well and all OK nodes accepted the second transaction with a higher Commission first, and the old one was forgotten later and discarded
Not really, RBF has been already available before Bitcoin Core 0.16 but it wasn't turned on for every transaction by default.
Edit: If the initial transaction is marked as replaceable, its inputs can be spent once again to different outputs if the transaction is forgot by your Bitcoin Core wallet (it can be done manually). The built-in "Bump fee" functionality forces users to decrease the change output's value and does not allow to modify other outputs. If the initial transaction is not marked as replaceable then most nodes will reject another transaction as a double-spend attempt.
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
Seems that your transaction still stuck after bumping the fee and set the transaction as final?
Like other said above, there's no way to delete this transaction once it's broadcasted.
If you want this transaction to confirm very soon you need to do CPFP(Child Pays For Parent) which will help to confirm this transaction(It still depends on your fee).
Follow these guides below how to do CPFP.
- A complete idiot's guide to child pays for parent?
Youtube guide
- How To Get Your Bitcoin Transaction Confirmed with CPFP
This video above you can follow it until 4:20 minutes then copy the generated raw TX then paste it on Electrum wallet you can find it on tools>Load transaction> From text then paste the raw transaction. This is only for safety for the private key you own.
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.
Have there been any changes in this regard with the time of Bitcoin Core 0.16? Then it was done well and all OK nodes accepted the second transaction with a higher Commission first, and the old one was forgotten later and discarded
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
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.
Thank you for your comprehensive answer, this is exactly what you needed to know how to do on the Electrum wallet
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
The first transaction will not be deleted from any node beside yours until your second transaction is confirmed (which does not have to be the case!).
All changes you do to your mempool are exclusively local on your node.
So the question is how to delete a transaction in Electrum
You can not delete transactions from the mempool of all nodes.
You can create a new transaction spending the same utxo's with a higher fee. This can (but does not have to!) lead to your second transaction being included into a block.
Jump to: