<p>One is per kilobyte, the other is a limit on the total.</p>

<p>The second will prevent a transaction from happening if it, following the first, has a too large fee.</p>

CC BY-SA 3.0
2015-08-04T12:43:49.940Z
Is it possible to pay fixed amount per transaction regardless the kilobytes?
Mohamed Farrag
CC BY-SA 3.0
2015-08-05T12:40:12.750Z
@Mohamed No, that wouldn't make sense. You're paying for space inside blocks, and miners prioritize transactions based on fee per byte. As you don't know the size of a transaction before creating it, specifying its exact fee would likely lead to unexpected behaviour.
Pieter Wuille
CC BY-SA 3.0
2017-10-01T06:00:02.720Z
https://btc.com/stats/unconfirmed-tx tells you how long your transaction will take to "clear" if you pay a certain transaction fee. Paying 0 may take too long, but you can get away with paying very little if you don't mind a delay in your transaction entering the blockchain.
Sun
CC BY-SA 3.0
2015-08-04T12:37:45.877Z
2015-08-04T12:37:45.877Z
Pieter Wuille
<p>In wallet options section it shows these two <a href="https://en.bitcoin.it/wiki/Running_Bitcoin" rel="nofollow">settings</a> </p>

<pre><code>-paytxfee=&lt;amt&gt;  Fee (in BTC/kB) to add to transactions you send (default: 0.00)  
-maxtxfee=&lt;amt&gt;  Maximum total fees to use in a single wallet transaction, setting too low may abort large transactions (default: 0.10)  
</code></pre>

<p>If I set these two settings in the bitcoin.conf which one will override the other ? or how does in work ?</p>

<bitcoind><bitcoin-core>
paytxfee vs maxtxfee which one overrides the other
Mohamed Farrag
# paytxfee vs maxtxfee which one overrides the other

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

In wallet options section it shows these two [settings](https://en.bitcoin.it/wiki/Running_Bitcoin)

```
-paytxfee=<amt>  Fee (in BTC/kB) to add to transactions you send (default: 0.00)  
-maxtxfee=<amt>  Maximum total fees to use in a single wallet transaction, setting too low may abort large transactions (default: 0.10)  

```

If I set these two settings in the bitcoin.conf which one will override the other ? or how does in work ?

**Tags:** bitcoind, bitcoin-core


---

## 1 answers

### Answer by username_1 on 2015-08-04. Score: 2 | Accepted answer

One is per kilobyte, the other is a limit on the total.

The second will prevent a transaction from happening if it, following the first, has a too large fee.

> **Comments:**
> **username_0**: Is it possible to pay fixed amount per transaction regardless the kilobytes?  
> **username_1**: @username_0 No, that wouldn't make sense. You're paying for space inside blocks, and miners prioritize transactions based on fee per byte. As you don't know the size of a transaction before creating it, specifying its exact fee would likely lead to unexpected behaviour.  
> **username_2**: https://btc.com/stats/unconfirmed-tx tells you how long your transaction will take to "clear" if you pay a certain transaction fee. Paying 0 may take too long, but you can get away with paying very little if you don't mind a delay in your transaction entering the blockchain.  

---

