<p>You can use Opt-in Replace By Fee to do this. Bitcoin Core already implements support for signaling Opt-in RBF and for increasing the fee later (with some caveats).</p>

<p>When creating a transaction from the command line, the <code>send*</code> commands have an optional argument named <code>replaceable</code>. If you set that to true, then the transaction created will automatically signal that it can be replaced in the future. To increase your fee, you then use the <code>bumpfee</code> command. Note that the command currently only works if the transaction has a change output. The fee will be deducted from the change output.</p>

<p>Note that these commands and the arguments are not necessarily listed on the bitcoin wiki (it is frequently out of date). To actually get the full listing of RPC commands, their arguments, and how to use them, use the <code>help</code> and <code>help &lt;command&gt;</code> commands.</p>

CC BY-SA 3.0
2017-12-17T18:44:02.600Z
2017-12-17T18:44:02.600Z
Ava Chow
<p>I have read that once a Bitcoin transaction is created, <a href="https://en.bitcoin.it/wiki/Transaction_expiration" rel="nofollow noreferrer">it never automatically expires</a>. In theory, a transaction could be created, get stuck at 0 confirmations for some years, and then all of a sudden confirm.</p>

<p>The proper way of increasing the fee would be to send another transaction that uses <strong>exactly the same coins</strong> as the first transaction.</p>

<p>How can I program the correct way via bitcoind?
Which <a href="https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list" rel="nofollow noreferrer">commands</a> should I use?</p>

<bitcoind><transaction-fees>
How to correctly implement the FEE increase using bitcoind?
Giancarlo
# How to correctly implement the FEE increase using bitcoind?

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

I have read that once a Bitcoin transaction is created, [it never automatically expires](https://en.bitcoin.it/wiki/Transaction_expiration). In theory, a transaction could be created, get stuck at 0 confirmations for some years, and then all of a sudden confirm.

The proper way of increasing the fee would be to send another transaction that uses **exactly the same coins** as the first transaction.

How can I program the correct way via bitcoind?
Which [commands](https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list) should I use?

**Tags:** bitcoind, transaction-fees


---

## 1 answers

### Answer by username_1 on 2017-12-17. Score: 1

You can use Opt-in Replace By Fee to do this. Bitcoin Core already implements support for signaling Opt-in RBF and for increasing the fee later (with some caveats).

When creating a transaction from the command line, the `send*` commands have an optional argument named `replaceable`. If you set that to true, then the transaction created will automatically signal that it can be replaced in the future. To increase your fee, you then use the `bumpfee` command. Note that the command currently only works if the transaction has a change output. The fee will be deducted from the change output.

Note that these commands and the arguments are not necessarily listed on the bitcoin wiki (it is frequently out of date). To actually get the full listing of RPC commands, their arguments, and how to use them, use the `help` and `help`  commands.


---

