<p>Although I've broadcasted many transactions via testnet with <a href="https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki" rel="nofollow noreferrer">RBF</a> opted-in ( <code>--rbf true</code>), yet, given different
incentives present among the miners of the testnet and of the mainnet, my experience so far does not seem very helpful when it comes to grasping firmly how RBF works in Electrum.
So far I've always broadcast them with 1 sat/byte. I most
cases they were picked up by miners with this fee. A couple of times I noticed a slight discrepancy between the fee that I did broadcast (always 1 sat/byte) and the fee (1.2-1.3 sat/byte) that was shown in <a href="https://mempool.space/" rel="nofollow noreferrer">the blockchain explorer</a>. Such minor discrepancies suggest to me that <a href="https://electrum.org/" rel="nofollow noreferrer">Electrum</a> somehow automates the process of bumping the fee up when needed.</p>
<p>Does Electrum handle incrementing the fee for me or do I have to manually bump the fee up? If the latter is the case,
can the fee bumping be done from the terminal (i.e. without <a href="https://en.wikipedia.org/wiki/Graphical_user_interface" rel="nofollow noreferrer">GUI</a>)?
If the logic of the wallet automates the RBF process, how does it look like exactly? How many blocks does it wait until it increments the fee? By what factor is the fee increased?
I have not found any information that would answer my questions in <a href="https://electrum.readthedocs.io/en/latest/" rel="nofollow noreferrer">Electrum's documentation</a>.</p>

CC BY-SA 4.0
2021-07-08T16:14:21.890Z
When you write "broadcast", I think you're actually referring to your transaction building instructions. I.e. you instructed your wallet to build with 1 sat/vB, but what was broadcast had a slightly higher feerate. I'm asking about that, because it could otherwise be understood that you first broadcast a transaction with the lower fee, but then saw an updated variant of the transaction later on the network, but I don't think the latter is what you mean.
Murch
CC BY-SA 4.0
2021-07-08T17:07:17.040Z
@Murch When I wrote ***Although I've broadcasted many transactions via testnet with RBF opted-in ( --rbf true)*** I meant that I broadcasted to the mempool, i.e. executed two commands: first `electrum payto` with `--rbf true` flag and then, after getting a long string of numbers in the output, `electrum broadcast long_string_of_numbers`. When I referred to ***the fee (1.2-1.3 sat/byte) that was shown in the blockchain explorer.*** I meant here the tx fee shown on some Bitcoin explorers, after being the tx have been confirmed.
John Smith
CC BY-SA 4.0
2021-07-08T17:52:15.860Z
Yeah, I guess it's just a small terminology nit: we would usually describe the first step as the transaction building and the second step where you submit the transaction to the network as the broadcast. The feerate is decided in the "payto" step where the transaction is built. Transactions are immutable after built, so the second step just allows you to either broadcast or refrain from broadcasting a fixed transaction.
Murch
<electrum><replace-by-fee><electrum-console>
Will electrum wallet increment the fee automatically or do I have to do it manually?
John Smith
# Will electrum wallet increment the fee automatically or do I have to do it manually?

(Asked by: username_0 on 2021-07-06)

Although I've broadcasted many transactions via testnet with [RBF](https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki) opted-in ( `--rbf true`), yet, given different
incentives present among the miners of the testnet and of the mainnet, my experience so far does not seem very helpful when it comes to grasping firmly how RBF works in Electrum.
So far I've always broadcast them with 1 sat/byte. I most
cases they were picked up by miners with this fee. A couple of times I noticed a slight discrepancy between the fee that I did broadcast (always 1 sat/byte) and the fee (1.2-1.3 sat/byte) that was shown in [the blockchain explorer](https://mempool.space/). Such minor discrepancies suggest to me that [Electrum](https://electrum.org/) somehow automates the process of bumping the fee up when needed.

Does Electrum handle incrementing the fee for me or do I have to manually bump the fee up? If the latter is the case,
can the fee bumping be done from the terminal (i.e. without [GUI](https://en.wikipedia.org/wiki/Graphical_user_interface))?
If the logic of the wallet automates the RBF process, how does it look like exactly? How many blocks does it wait until it increments the fee? By what factor is the fee increased?
I have not found any information that would answer my questions in [Electrum's documentation](https://electrum.readthedocs.io/en/latest/).

**Tags:** electrum, replace-by-fee, electrum-console

> **Comments:**
> **username_1**: When you write "broadcast", I think you're actually referring to your transaction building instructions. I.e. you instructed your wallet to build with 1 sat/vB, but what was broadcast had a slightly higher feerate. I'm asking about that, because it could otherwise be understood that you first broadcast a transaction with the lower fee, but then saw an updated variant of the transaction later on the network, but I don't think the latter is what you mean.  
> **username_0**: @username_1 When I wrote ***Although I've broadcasted many transactions via testnet with RBF opted-in ( --rbf true)*** I meant that I broadcasted to the mempool, i.e. executed two commands: first `electrum payto` with `--rbf true` flag and then, after getting a long string of numbers in the output, `electrum broadcast long_string_of_numbers`. When I referred to ***the fee (1.2-1.3 sat/byte) that was shown in the blockchain explorer.*** I meant here the tx fee shown on some Bitcoin explorers, after being the tx have been confirmed.  
> **username_1**: Yeah, I guess it's just a small terminology nit: we would usually describe the first step as the transaction building and the second step where you submit the transaction to the network as the broadcast. The feerate is decided in the "payto" step where the transaction is built. Transactions are immutable after built, so the second step just allows you to either broadcast or refrain from broadcasting a fixed transaction.  

---

## 0 answers

