<p><strong>First: remind <code>settxfee</code> is not a absolute fee per transaction. <em>It's a fee per kilobyte</em></strong>.</p>

<p>Example:</p>

<ol>
<li>Alice sends 1BTC to Bob</li>
<li>Alice has 11 times 0.1 BTC in her wallet (she received 11 times 0.1 BTC from different persons)</li>
<li>Alice transaction will require all 11 x 0.1BTC inputs to create the 1BTC-to-Bob-transaction</li>
<li>Therefore the transaction is bigger (in terms of bytesize) then if she would hold 1 x 1.1BTC in her wallet.</li>
</ol>

<p>Bitcoin-Core will only accept transaction to it's mempool which contains the minimum fee.</p>

CC BY-SA 3.0
2015-07-02T18:54:57.723Z
2015-07-02T18:54:57.723Z
Jonas Schnelli
<p>Yes, if you use settxfee that overrides and it will use that set amount.</p>

CC BY-SA 3.0
2015-05-04T17:50:20.363Z
Should I set that in the .conf file or as bitcoin-cli command?
CryptoPanda
CC BY-SA 3.0
2015-05-05T19:06:08.013Z
@CryptoPanda Personally I do it through RPC/bitcoin-cli as I don't restart my node(s) very often.
George
CC BY-SA 3.0
2015-05-07T11:00:35.147Z
Ok I'll try that
Does that way of setting it stays after restart?
CryptoPanda
CC BY-SA 3.0
2015-05-08T17:53:58.920Z
@CryptoPanda No, I don't think it does. You could use the -maxtxfee=<amt> parameter on startup perhaps.
George
CC BY-SA 3.0
2015-05-03T15:36:04.740Z
2015-05-03T15:36:04.740Z
George
<p>I'm running bitcoind for a service that works with quite small user withdraws most of the time.
Recently I noticed that instead of the standard 0.0001 tx fee from the recent past, it already charges up to 0.0008 for some transactions which I find expensive for this specific use case. (I read about that update to dynamic fees but then forgot about it)</p>

<p>getinfo gives "paytxfee" : 0.00000000" by the way.
I haven't explicitly set the fee in bitcoin.conf</p>

<p>So, if one doesn't want to take advantage of the dynamic fee but set a fixed one 
- How is best to do it? Just "bitcoin-cli settxfee 0.0001" or in the .conf file? Would it actually be enforced or it will still disregard it in some cases?
- if it actually works to set it as fixed, how do you think that would affect the confirmation time? Will 0.0001 be fairly enough for the time being to get in the very next block?</p>

CC BY-SA 3.0
2015-04-30T18:16:18.303Z
Can you give the txid of such a transaction, so we can see its details? One possibility is that the transaction is larger than 1 kb (the standard fee is  btc 0.0001 per kb).
Nate Eldredge
CC BY-SA 3.0
2015-05-02T12:55:56.027Z
Yes, here is one
https://blockchain.info/tx/3db46410c589383320dc0ab12cc884f8c36201f40c9bc57f4c8e18b1413b0759

This particular one is for bigger amount but still, since it's 1257 bytes should be able to be sent just fine for 0.0002 fee right?
CryptoPanda
<bitcoind>
Taking control of the dynamic bitcoind tx fee
CryptoPanda
# Taking control of the dynamic bitcoind tx fee

(Asked by: username_0 on 2015-04-30)

I'm running bitcoind for a service that works with quite small user withdraws most of the time.
Recently I noticed that instead of the standard 0.0001 tx fee from the recent past, it already charges up to 0.0008 for some transactions which I find expensive for this specific use case. (I read about that update to dynamic fees but then forgot about it)

getinfo gives "paytxfee" : 0.00000000" by the way.
I haven't explicitly set the fee in bitcoin.conf

So, if one doesn't want to take advantage of the dynamic fee but set a fixed one
- How is best to do it? Just "bitcoin-cli settxfee 0.0001" or in the .conf file? Would it actually be enforced or it will still disregard it in some cases?
- if it actually works to set it as fixed, how do you think that would affect the confirmation time? Will 0.0001 be fairly enough for the time being to get in the very next block?

**Tags:** bitcoind

> **Comments:**
> **username_1**: Can you give the txid of such a transaction, so we can see its details? One possibility is that the transaction is larger than 1 kb (the standard fee is  btc 0.0001 per kb).  
> **username_0**: Yes, here is one https://blockchain.info/tx/3db46410c589383320dc0ab12cc884f8c36201f40c9bc57f4c8e18b1413b0759  This particular one is for bigger amount but still, since it's 1257 bytes should be able to be sent just fine for 0.0002 fee right?  

---

## 2 answers

### Answer by username_2 on 2015-07-02. Score: 2

**First: remind `settxfee` is not a absolute fee per transaction. *It's a fee per kilobyte***.

Example:

1. Alice sends 1BTC to Bob
2. Alice has 11 times 0.1 BTC in her wallet (she received 11 times 0.1 BTC from different persons)
3. Alice transaction will require all 11 x 0.1BTC inputs to create the 1BTC-to-Bob-transaction
4. Therefore the transaction is bigger (in terms of bytesize) then if she would hold 1 x 1.1BTC in her wallet.

Bitcoin-Core will only accept transaction to it's mempool which contains the minimum fee.


---

### Answer by username_3 on 2015-05-03. Score: 0

Yes, if you use settxfee that overrides and it will use that set amount.

> **Comments:**
> **username_0**: Should I set that in the .conf file or as bitcoin-cli command?  
> **username_3**: @username_0 Personally I do it through RPC/bitcoin-cli as I don't restart my node(s) very often.  
> **username_0**: Ok I'll try that Does that way of setting it stays after restart?  
> **username_3**: @username_0 No, I don't think it does. You could use the -maxtxfee=<amt> parameter on startup perhaps.  

---

