<p>The <code>bumpfee</code> RPC command takes a <code>"totalFee"</code> argument. When passed, this is the total fee that will be used for the replacing transaction.</p>

CC BY-SA 4.0
2021-05-17T14:34:22.030Z
Thank you. That sounds like the optimal way to do it.
I didn't find such an option back when I searched for it, and used a different solution, but that's what I'll do in the future.
yuvalm2
CC BY-SA 4.0
2018-06-03T23:53:26.707Z
2018-06-03T23:53:26.707Z
Pieter Wuille
<p>Increasing in steps is very weird, and should not be done. You may have a look at <a href="https://bitcoin.stackexchange.com/a/54457/63522">this canonical answer</a>, under the section "How to make a Full RBF transaction / Bitcoin Core".</p>

<p>For me, to get rid of the unconfirmed transaction, I needed to remove the mempool.dat file, the other approaches did not work. Then followed the advice given:</p>

<blockquote>
  <p>Once the transaction is either Abandoned or cleared from the wallet, you can simply go to the Send tab and send the Bitcoin again but make sure that you include a sufficient transaction fee.</p>
</blockquote>

<p>I finally succeeded in having a confirmed transaction after one single replacement with an appropriate fee.</p>

CC BY-SA 3.0
2017-12-21T09:10:12.880Z
Yes, thanks.
That's what I did and it worked well. Not sure why the wallet is implemented the way it is, though. (And I would expect this action to be doable without restarting the program, deleting files etc.)
yuvalm2
CC BY-SA 3.0
2017-12-20T08:09:17.973Z
2017-12-20T08:09:17.973Z
nulldev
<p>Instead, what I did was to run the wallet again and make it forget unconfirmed transactions using:</p>

<pre><code>C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe --zapwallettxes=1
</code></pre>

<p>And removed my local copy of the mempool. (A file called mempool.dat in bitcoin's data folder)</p>

<p>(Took about an hour to rescan)</p>

<p>And then making another transaction to the same destination with higher fees (Made from the same source node, so only one of these transactions could occur, nullifying the other)</p>

CC BY-SA 3.0
2017-12-20T07:06:53.760Z
2017-12-21T09:09:00.077Z
2017-12-21T09:09:00.077Z
yuvalm2
<p>I marked my transaction with "Request replace-By-Fee"* in my bitcoin core wallet, and now while I can increase the transaction fee, I can only increase it by a tiny bit, and I can't set it to what I really need. (forcing me to increase the fees 15 times in a row)</p>

<p>Is there any simple way for me to increase the fee more significantly without creating all of these intermediate transactions?</p>

<pre><code>* By the way, a very bad name for "allow future fees increase"
</code></pre>

CC BY-SA 3.0
2018-02-27T08:24:32.397Z
Depending on what version of Bitcoin Core you are running. In v0.15.1 the minimum fee bump is significant.
Willtech
CC BY-SA 3.0
2018-02-28T15:27:47.290Z
fee bumping is a very weird way to change the fees. I should be able to set it to whatever I believe is the correct value now. There is no reason it would always go up in a certain quantum.
yuvalm2
CC BY-SA 3.0
2018-03-01T08:00:57.613Z
There is a minimum increase specified (by consensus I believe) to prevent a fee mini-bump attack, too expensive now that the minimum bump is set higher.
Willtech
<bitcoin-core><transaction-fees><replace-by-fee>
Increase a transaction fee in bitcoin core
yuvalm2
# Increase a transaction fee in bitcoin core

(Asked by: username_0 on 2017-12-19)

I marked my transaction with "Request replace-By-Fee"\* in my bitcoin core wallet, and now while I can increase the transaction fee, I can only increase it by a tiny bit, and I can't set it to what I really need. (forcing me to increase the fees 15 times in a row)

Is there any simple way for me to increase the fee more significantly without creating all of these intermediate transactions?

```
* By the way, a very bad name for "allow future fees increase"

```

**Tags:** bitcoin-core, transaction-fees, replace-by-fee

> **Comments:**
> **username_1**: Depending on what version of Bitcoin Core you are running. In v0.15.1 the minimum fee bump is significant.  
> **username_0**: fee bumping is a very weird way to change the fees. I should be able to set it to whatever I believe is the correct value now. There is no reason it would always go up in a certain quantum.  
> **username_1**: There is a minimum increase specified (by consensus I believe) to prevent a fee mini-bump attack, too expensive now that the minimum bump is set higher.  

---

## 3 answers

### Answer by username_2 on 2018-06-03. Score: 2 | Accepted answer

The `bumpfee` RPC command takes a `"totalFee"` argument. When passed, this is the total fee that will be used for the replacing transaction.

> **Comments:**
> **username_0**: Thank you. That sounds like the optimal way to do it. I didn't find such an option back when I searched for it, and used a different solution, but that's what I'll do in the future.  

---

### Answer by username_3 on 2017-12-20. Score: 0

Increasing in steps is very weird, and should not be done. You may have a look at [this canonical answer](https://bitcoin.stackexchange.com/a/54457/63522), under the section "How to make a Full RBF transaction / Bitcoin Core".

For me, to get rid of the unconfirmed transaction, I needed to remove the mempool.dat file, the other approaches did not work. Then followed the advice given:

> Once the transaction is either Abandoned or cleared from the wallet, you can simply go to the Send tab and send the Bitcoin again but make sure that you include a sufficient transaction fee.

I finally succeeded in having a confirmed transaction after one single replacement with an appropriate fee.

> **Comments:**
> **username_0**: Yes, thanks. That's what I did and it worked well. Not sure why the wallet is implemented the way it is, though. (And I would expect this action to be doable without restarting the program, deleting files etc.)  

---

### Answer by username_0 on 2017-12-20. Score: -1

Instead, what I did was to run the wallet again and make it forget unconfirmed transactions using:

```
C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe --zapwallettxes=1

```

And removed my local copy of the mempool. (A file called mempool.dat in bitcoin's data folder)

(Took about an hour to rescan)

And then making another transaction to the same destination with higher fees (Made from the same source node, so only one of these transactions could occur, nullifying the other)


---

