<blockquote>
  <p>Why the move towards variable Tx fees?</p>
</blockquote>

<p>Almost all miners choose what transactions to include in blocks based on fees and priority relative to byte size, so transactions that pay higher fees are more likely to be included in the next block than similar-size transactions that pay lower fees.</p>

<p>Advanced users have always been able to take advantage of this mechanism to set their fee higher for transactions they want to confirm quickly and lower when they don't mind waiting for a while.  But to do this right has always required manually looking at recent blocks to see what were the lowest fee or lowest priority transactions they accepted, which put this kind of "fee market" out of reach of everyday users (or advanced users who don't want to spend much time pinching pennies).</p>

<p>However, Gavin Andresen <a href="https://github.com/bitcoin/bitcoin/pull/3959" rel="nofollow noreferrer">introduced code</a> into Bitcoin Core 0.10.0 to automatically have each Bitcoin Core node keep its own statistics about block fee and priority thresholds, so now you can run a simple command like this,</p>

<pre><code>$ bitcoin-cli estimatefee 25
0.00001919
</code></pre>

<p>to see that if you don't mind waiting up to 25 blocks for confirmation, you can probably set your fee to 0.00001919 per kilobyte.</p>

<p>Thanks the the work of several volunteers, the Bitcoin Core GUI now also uses this information to allow everyday users to easily choose between fast confirmation and low fees.</p>

<p><a href="https://i.sstatic.net/tDW6o.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/tDW6o.png" alt="enter image description here"></a><br>
<sub>(source: <a href="http://bitcoinillustrated.org/images/2015-02-24-071217_879x545_scrot.png" rel="nofollow noreferrer">bitcoinillustrated.org</a>)</sub></p>

<p>This really gives the fee market a chance to develop so that Bitcoin Core can automatically adjust to things like filled (max-size) blocks, new larger blocks, changing use patterns, and significant changes in BTC/fiat exchange rates.  It is also hoped that some safe way will be found to allow SPV clients to also estimate fees and priority so that they can offer their users the same informed choices.</p>

<blockquote>
  <p>Is the 0.0001 BTC fee deprecated?</p>
</blockquote>

<p>Yes, mostly.  It's still the default if not enough information can be gathered from the network.</p>

<p>There is also still unchanged the default relay fee of 0.00001 BTC per kilobyte.  This isn't related to transactions you create but rather the transactions your node will accept for relay.  The default is widely used, so paying less than it is not a good idea.</p>

CC BY-SA 3.0
2015-02-25T09:07:22.020Z
Can you comment on how *dust Txns* fit into this? Is It still 5600 satoshis?
Wizard Of Ozzie
CC BY-SA 3.0
2015-02-25T12:33:28.573Z
A dust tx is a transaction with a too-small output.  By default nodes won't relay dust txes at all and miners won't mine them, so they won't confirm no matter how high you set your fee.  The current default dust threshold for P2PKH and P2SH outputs is 546 satoshis.  For more details, see my answer [here](http://bitcoin.stackexchange.com/questions/30370/are-transactions-containing-zero-value-output-accepted-by-miners/35519#35519) about dust.
David A. Harding
CC BY-SA 3.0
2017-07-06T18:42:43.730Z
Thanks for your answer. So then how do we figure out how many kilobytes a transaction will be?
Marc Alexander
CC BY-SA 4.0
2015-02-24T12:26:05.053Z
2019-03-14T16:37:04.540Z
2019-03-14T16:37:04.540Z
David A. Harding
<p>I'm looking for clarification of the new Tx priority and Tx Fees settings (eg <em>fee per kB</em> in the <code>0.10</code> version of Bitcoincore. Is the 0.0001 BTC fee deprecated? Why the move towards variable Tx fees?</p>

<transactions><transaction-fees><bitcoin-core>
Clarification of Tx Fees settings in Bitcoincore 0.10
Wizard Of Ozzie
# Clarification of Tx Fees settings in Bitcoincore 0.10

(Asked by: username_0 on 2015-02-24)

I'm looking for clarification of the new Tx priority and Tx Fees settings (eg *fee per kB* in the `0.10` version of Bitcoincore. Is the 0.0001 BTC fee deprecated? Why the move towards variable Tx fees?

**Tags:** transactions, transaction-fees, bitcoin-core


---

## 1 answers

### Answer by username_1 on 2015-02-24. Score: 2 | Accepted answer

> Why the move towards variable Tx fees?

Almost all miners choose what transactions to include in blocks based on fees and priority relative to byte size, so transactions that pay higher fees are more likely to be included in the next block than similar-size transactions that pay lower fees.

Advanced users have always been able to take advantage of this mechanism to set their fee higher for transactions they want to confirm quickly and lower when they don't mind waiting for a while. But to do this right has always required manually looking at recent blocks to see what were the lowest fee or lowest priority transactions they accepted, which put this kind of "fee market" out of reach of everyday users (or advanced users who don't want to spend much time pinching pennies).

However, Gavin Andresen [introduced code](https://github.com/bitcoin/bitcoin/pull/3959) into Bitcoin Core 0.10.0 to automatically have each Bitcoin Core node keep its own statistics about block fee and priority thresholds, so now you can run a simple command like this,

```
$ bitcoin-cli estimatefee 25
0.00001919

```

to see that if you don't mind waiting up to 25 blocks for confirmation, you can probably set your fee to 0.00001919 per kilobyte.

Thanks the the work of several volunteers, the Bitcoin Core GUI now also uses this information to allow everyday users to easily choose between fast confirmation and low fees.

[![enter image description here](https://i.sstatic.net/tDW6o.png)](https://i.sstatic.net/tDW6o.png)  
(source: [bitcoinillustrated.org](http://bitcoinillustrated.org/images/2015-02-24-071217_879x545_scrot.png))

This really gives the fee market a chance to develop so that Bitcoin Core can automatically adjust to things like filled (max-size) blocks, new larger blocks, changing use patterns, and significant changes in BTC/fiat exchange rates. It is also hoped that some safe way will be found to allow SPV clients to also estimate fees and priority so that they can offer their users the same informed choices.

> Is the 0.0001 BTC fee deprecated?

Yes, mostly. It's still the default if not enough information can be gathered from the network.

There is also still unchanged the default relay fee of 0.00001 BTC per kilobyte. This isn't related to transactions you create but rather the transactions your node will accept for relay. The default is widely used, so paying less than it is not a good idea.

> **Comments:**
> **username_0**: Can you comment on how *dust Txns* fit into this? Is It still 5600 satoshis?  
> **username_1**: A dust tx is a transaction with a too-small output.  By default nodes won't relay dust txes at all and miners won't mine them, so they won't confirm no matter how high you set your fee.  The current default dust threshold for P2PKH and P2SH outputs is 546 satoshis.  For more details, see my answer [here](http://bitcoin.stackexchange.com/questions/30370/are-transactions-containing-zero-value-output-accepted-by-miners/35519#35519) about dust.  
> **username_2**: Thanks for your answer. So then how do we figure out how many kilobytes a transaction will be?  

---

