Topic: Bump fee window (Read 673 times)

Must have been a "glitch in the matrix" then

Possibly some sort of corruption in the wallet file or something that was causing it to send or request "bad" data from the servers which was getting your client disconnected/timed out (banned? )... I've honestly never seen that behaviour before.

Glad you managed to fix it by simply rebuilding the wallet tho.

Nothing installed, clean Win10.

Removed the wallet and rebuilt it from seed - everything was ok.

68 isn't that many in the grand scheme of things... if it was several hundred or 1000+ or something, then it might cause the throttling... but 68 shouldn't really trigger that.

And even stranger that it works perfectly on a different PC... there must be something in the setup of that specific PC that is causing the connections to go crazy like that... some AntiVirus/AntiMalware or firewall perhaps?

68. Rare long-term investment wallet. There is no such thing on another PC on this wallet

Approximately how many transactions and/or addresses are in that specific wallet?

It could be that your wallet simply has too many transactions and/or is requesting info for too many addresses at once... because of that the servers are throttling your connection... Once it is throttled, the "ElectrumX" server (which most Electrum Servers are running) will remember your IP and refuse your connection until a specified timeout period has passed.

Thank you. And as you can see there is a violation in that transaction of mine that may break one of their preferences (standard rules) such as RBF fee bump? After all, I did it using Electrum tools, simply by increasing the original transaction by 2 times

It is so only on this wallet, so I shot a video where everything is ok, but it is worth opening this wallet and the one that was opened also loses the network
https://drive.google.com/file/d/1LsuhPjTXFWGwkVKth2yQ8FB5XAXMepkZ/view?usp=sharing

https://live.blockcypher.com/btc/pushtx/
you will have to paste your entire tranasction hex (like what you posted in an earlier comment here) in this textbox and press broadcast.
keep in mind that there is no guarantee that other nodes would accept a transaction that may break one of their preferences (standard rules) such as RBF fee bump.

It seems that there is something blocking your Electrum to connect in any Electrum server.

Are you using a VPN? Try to disable it and try again. If not, then try to change your PC/Laptop DNS.

You can choose any of these DNS below.
- 8.8.8.8 and 8.8.4.4 = Google DNS
- 1.1.1.1 and 1.0.0.1 = Cloudflare DNS

After you manually set the DNS, follow this.

- Open CMD
- Type "ipconfig /release" then enter
- Type "ipconfig /renew" then enter
- Type "ipconfig /flushdns" then enter

Then try to check your Electrum again if the circle turns to green.

The program cannot connect, synchronize. Constantly trying and in no way, if you press the button on the arrows - you can see that it is trying to different servers all the time

https://drive.google.com/file/d/1TV1y63VIqahil7TX_m4FmyCNUAMJrM4h/view?usp=sharing

I tried to find him - but who found it seems to be unable to do broadcast there. You can get a link to the service Blockcypher where brodcast it? I'll try it myself next time I need it again.

Mine has no problem with synchronization.

Seems like you've been being disconnected from your selected server again and again, try to connect to other servers.
If you're using your own and it's outdated, upgrade to the latest version (probably related: Electrum 4.0.2 keeps Synchronizing)

BTW, that was off-topic... and the number below that's being updated is the total number of addresses in your wallet + new UTXOs.

Could've been me. I went to try to broadcast the transaction everywhere and found that Blockcypher doesn't follow the RBF fee increment rule (or didn't see your old transaction). You could've lucked out and Blockcypher relayed it to a miner who also doesn't care about the amount of fee increment.

I would say that it's an outlier and you would usually have to increase the fee enough to meet the requirement.

And what kind of garbage is this today on the 24th, Electrum 4.0.2 is constantly synchronized at the entrance to the program and cannot finish it: at the bottom, the numbers are constantly updated and the circle is green or red, then the arrows are synchronized with the network

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.

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.

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 change outputs, I did two into one

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.

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


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

Might be an issue with how coinb.in calculate fees/byte. Could you paste the raw TX here?

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.

Yes, twice (x2)


Good thing, but also writes an error

I have updated my reply with more accurate information. Now, it should reflect what you were talking about.

It's RBF. Is your replacement transaction having a larger fee per byte than your first transaction?
Just a web utility tool for you to submit transactions to the network[1].

[1] coinb.in/#broadcast

What is this tool? how do I use it? The transaction is ready and signed by all cosigners, it remains to send out

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

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

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.
TXID has to be in a quotation. For example:

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

After executing this command, nothing happened

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

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.

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

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

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

Not really, RBF has been already available before Bitcoin Core 0.16 but it wasn't turned on for every transaction by default. If you increase your transaction fee using RBF, you decrease one of your output's value; you don't add new ones or remove them completely. Such transaction replaces the old one without any problems. 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.

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.

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.

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

Thank you for your comprehensive answer, this is exactly what you needed to know how to do on the Electrum wallet

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.



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.

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?