<p>You can change the maxmempool setting to achieve this. </p>

<p><a href="https://gist.github.com/laanwj/efe29c7661ce9b6620a7" rel="nofollow">https://gist.github.com/laanwj/efe29c7661ce9b6620a7</a></p>

CC BY-SA 3.0
2016-10-27T15:50:38.460Z
Please include the relevant information in your post, link only answers are considered low-quality and may be removed. If you found the information on another page, adding a link to the source is appreciated of course.
Murch
CC BY-SA 3.0
2016-10-27T03:49:18.043Z
2016-10-27T03:49:18.043Z
dark knight
<p>You can increase the mempool size, if you have an interest in seeing transactions that likely won't confirm for a very long time, but you certainly don't have to. The mempool is sorted by feerate, and when the limiter kicks in, it removes the lowest feerate transactions. Since miners sort by feerate, and can include only a limited number of transactions per block, the mempool effectively works as a queue.</p>

<p>By design, you will not always be able to store all unconfirmed transactions. If your goal would be to have all, and crank up your memory pool to accomodate this, someone could just start creating an infinite stream of transactions sending back and forth, until your node goes out of memory. This is the reason why the mempool size is limited in the first place: protection against a denial of service on the network.</p>

CC BY-SA 3.0
2016-10-27T05:28:18.020Z
2016-10-27T06:01:50.780Z
2016-10-27T06:01:50.780Z
Pieter Wuille
<p>I am seeing 68k unconfirmed transactions on <a href="https://blockchain.info/unconfirmed-transactions" rel="noreferrer">blockchain.info</a>. My own <code>bitcoind</code> (<code>v0.13.0</code>) node has 49k transactions in its mempool with memory usage currently at 230mb. Knowing that the memory cap is currently at 300mb, I fear that very soon my node will not be able to keep all unconfirmed transactions. Should I increase this cap as a temporary measure until things get better? if so, how do I do that?</p>

CC BY-SA 4.0
2024-01-11T16:19:14.933Z
Related/possible duplicate: https://bitcoin.stackexchange.com/q/118137/5406
Murch
<bitcoind><bitcoin-core><unconfirmed-transactions><mempool>
Should I increase my mempool size to accomodate temporary crisis?
Sven Williamson
# Should I increase my mempool size to accomodate temporary crisis?

(Asked by: username_0 on 2016-10-26)

I am seeing 68k unconfirmed transactions on [blockchain.info](https://blockchain.info/unconfirmed-transactions). My own `bitcoind` (`v0.13.0`) node has 49k transactions in its mempool with memory usage currently at 230mb. Knowing that the memory cap is currently at 300mb, I fear that very soon my node will not be able to keep all unconfirmed transactions. Should I increase this cap as a temporary measure until things get better? if so, how do I do that?

**Tags:** bitcoind, bitcoin-core, unconfirmed-transactions, mempool

> **Comments:**
> **username_1**: Related/possible duplicate: https://bitcoin.stackexchange.com/q/118137/5406  

---

## 2 answers

### Answer by username_3 on 2016-10-27. Score: 4 | Accepted answer

You can increase the mempool size, if you have an interest in seeing transactions that likely won't confirm for a very long time, but you certainly don't have to. The mempool is sorted by feerate, and when the limiter kicks in, it removes the lowest feerate transactions. Since miners sort by feerate, and can include only a limited number of transactions per block, the mempool effectively works as a queue.

By design, you will not always be able to store all unconfirmed transactions. If your goal would be to have all, and crank up your memory pool to accomodate this, someone could just start creating an infinite stream of transactions sending back and forth, until your node goes out of memory. This is the reason why the mempool size is limited in the first place: protection against a denial of service on the network.


---

### Answer by username_2 on 2016-10-27. Score: 1

You can change the maxmempool setting to achieve this.

<https://gist.github.com/laanwj/efe29c7661ce9b6620a7>

> **Comments:**
> **username_1**: Please include the relevant information in your post, link only answers are considered low-quality and may be removed. If you found the information on another page, adding a link to the source is appreciated of course.  

---

