Bump fee window

[DigitalMonster]

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

[DigitalMonster]

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

[ranochigo]

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.

If you want to remove any transactions, use the following command in your console.

Code:

wallet.remove_transaction(txid_here)

[DigitalMonster]

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

[DigitalMonster]

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):
>> 

[ranochigo]

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

Code:

>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>> 

TXID has to be in a quotation. For example:

Code:

wallet.remove_transaction('1ff95e3c5fced8284f91598583e109a614996f4c1f0ce072631a6611b71d14fe')

After executing the command, you can proceed to spend the funds again in the send tab.

[DigitalMonster]

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

Code:

>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>> 

TXID has to be in a quotation. For example:

Code:

wallet.remove_transaction('1ff95e3c5fced8284f91598583e109a614996f4c1f0ce072631a6611b71d14fe')

After executing the command, you can proceed to spend the funds again in the send tab.

Super! This command is similar to replace this whole complicated process in the instruction manual deletion from the file. Now I will try to create a new transaction with an increased Commission so that it is recorded in the blockchain forced the nodes to discard the first one, which, as when I did on the BitCoin Core wallet, if nothing has changed, everything should also work

[DigitalMonster]

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

Code:

>> wallet.remove_transaction(e87ee92e1fe83bfc59e8abf1b0d1096990de43254e0847262f0ef6882ea88aac)
Traceback (most recent call last):
>> 

TXID has to be in a quotation. For example:

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

[DigitalMonster]

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

[ranochigo]

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?

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

[Rath_]

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.

[DigitalMonster]

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

Good thing, but also writes an error

[Abdussamad]

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.

[ranochigo]

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?

[mocacinno]

I'm not really following the discussion, but maybe the broadcasting fails because of this

The replacement transaction must pay for its own bandwidth in addition to the amount paid by the original transactions at least by the rate set by the node's minimum relay fee setting. For example, if the minimum relay fee is 1 satoshi/byte and the replacement transaction is 500 bytes total, then the replacement must pay a fee at least 500 satoshis higher than the originals.

source: https://en.bitcoin.it/wiki/Transaction_replacement

[HCP]

Yeah... you can't just pay any higher amount... there is a certain minimum threshold that you have to cross to get it accepted.

Unfortunately, it's not a "fixed" amount as such... it depends on transaction sizes and fee rate used for the original transaction etc. So, trying to do this manually can require a bit of calculating (and/or experimenting) to make it work.

I believe it is done this way to prevent a possible DoS attack scenario, by making it "expensive".

I did a manual RBF about 2 weeks ago during the previous price pump... and do know that I was able to pay a lot less than the "minimum" that Bitcoin Core was trying to use... from memory it was still 5-6x the original fee... ~400 sats vs. ~2500 sats... for a transaction that was around 400 vbytes (~1600 WU)...

Bitcoin Core wanted me to pay like ~50000 sats as the "bump fee" But I suspect it was also doing confirmation time calcs and trying to get within 25 blocks etc.

[DigitalMonster]

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.

I change outputs, I did two into one

[DigitalMonster]

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?

02000000000101a7fe8ba463c9cd400097220533d7c81b02a0104e3a760c4bbb933eaa9ebdedaf0 000000000fdffffff0162d8010000000000160014dadcd7f1cd1b11c3a69f61585f003395ec8a99 550400473044022056b0b1deb00b4f2a798623849655316b2b8cb35fb5607a162fd6cdc5b235165 702203395c5e20e5425a2eacab3c827e44083eb3fdd05398dd2213a23b551db7127680147304402 2065c5deee5467bdbcceb7974effd5ef02e62c57f75e0c7b3a085027351254c5fe022047a8caf51 45052d8f3c54d1f1d829b14cb566a0f7beba2a3dbea9a0a283cfed701475221024d34631e9abc48 8b9a9d137bc91746415acbadbe42b5122a83d514f7cf1f11482103608484ccf6e229ee06d3358c5 49e458c5a2d8c56e8b9eaa89413e3509593fdb652aeafd50900

https://drive.google.com/file/d/1stpCM-xB6DAi54OhztbHYaNs8P_2bhx4/view?usp=sharing and here the transaction is a format Electrum

[ranochigo]

02000000000101a7fe8ba463c9cd400097220533d7c81b02a0104e3a760c4bbb933eaa9ebdedaf0 000000000fdffffff0162d8010000000000160014dadcd7f1cd1b11c3a69f61585f003395ec8a99 550400473044022056b0b1deb00b4f2a798623849655316b2b8cb35fb5607a162fd6cdc5b235165 702203395c5e20e5425a2eacab3c827e44083eb3fdd05398dd2213a23b551db7127680147304402 2065c5deee5467bdbcceb7974effd5ef02e62c57f75e0c7b3a085027351254c5fe022047a8caf51 45052d8f3c54d1f1d829b14cb566a0f7beba2a3dbea9a0a283cfed701475221024d34631e9abc48 8b9a9d137bc91746415acbadbe42b5122a83d514f7cf1f11482103608484ccf6e229ee06d3358c5 49e458c5a2d8c56e8b9eaa89413e3509593fdb652aeafd50900

https://drive.google.com/file/d/1stpCM-xB6DAi54OhztbHYaNs8P_2bhx4/view?usp=sharing and here the transaction is a format Electrum

I looked at the transaction that you're trying to replace. It doesn't have enough incremental fee.

The reference node requires that the new transaction to pay an additional fee (amounting to a network relay fee) to the previous transaction. Failing which, the reference node will refuse to relay the transaction resulting in a poor propagation. Try paying an additional 0.00000073BTC.

[DigitalMonster]

02000000000101a7fe8ba463c9cd400097220533d7c81b02a0104e3a760c4bbb933eaa9ebdedaf0 000000000fdffffff0162d8010000000000160014dadcd7f1cd1b11c3a69f61585f003395ec8a99 550400473044022056b0b1deb00b4f2a798623849655316b2b8cb35fb5607a162fd6cdc5b235165 702203395c5e20e5425a2eacab3c827e44083eb3fdd05398dd2213a23b551db7127680147304402 2065c5deee5467bdbcceb7974effd5ef02e62c57f75e0c7b3a085027351254c5fe022047a8caf51 45052d8f3c54d1f1d829b14cb566a0f7beba2a3dbea9a0a283cfed701475221024d34631e9abc48 8b9a9d137bc91746415acbadbe42b5122a83d514f7cf1f11482103608484ccf6e229ee06d3358c5 49e458c5a2d8c56e8b9eaa89413e3509593fdb652aeafd50900

https://drive.google.com/file/d/1stpCM-xB6DAi54OhztbHYaNs8P_2bhx4/view?usp=sharing and here the transaction is a format Electrum

I looked at the transaction that you're trying to replace. It doesn't have enough incremental fee.

The reference node requires that the new transaction to pay an additional fee (amounting to a network relay fee) to the previous transaction. Failing which, the reference node will refuse to relay the transaction resulting in a poor propagation. Try paying an additional 0.00000073BTC.

Can you imagine, now I went to see the answers here, and found that the transaction that I could not broadcast this one above, had logged 244 blocks back to the blockchain successfully. this is nonsense, it turns out Electrum or there on the site one of them did it.