<p>Default value for mempoolexpiry is 336. That is two weeks. Your value is 48 so that means that a transaction in your mempool for more than 2 days will be dropped. I consider that value to be inappropriate (too low) given the current mempool size (+300 blocks). Is there any reason for that value in your node?</p>
<p>Also, any node do not (re)transmit txs that are already on the mempoool. That is a anti-spam measurement. It's possible that you received the transaction when you were starting your node (poorly connected) by another starting node also poorly connected, so that transaction got stuck in both mempools. Also the agent (maybe yourself) that send the transaction in first place has not re-transmitted the transaction since then.</p>
<p>There is no way to remove that tx from your mempool but you can rebroadcast it again by other means (i.e. <a href="https://bitaccelerate.com/pushtx/" rel="nofollow noreferrer">https://bitaccelerate.com/pushtx/</a>) and wait to be mined.</p>
<p>I've also found that my node (which feeds my webpage <a href="https://mempoolexplorer.com" rel="nofollow noreferrer">https://mempoolexplorer.com</a>) sometimes has transactions that any other service have. Maybe for the same reason.</p>

CC BY-SA 4.0
2023-11-21T18:50:00.437Z
2 days works for our specific usecase. If the txn is indeed mined after a week, it will be synced anyway as part of new block data. So this hasn't caused any problems.

In fact, I'm looking at a way to drop (or purge) txns even before 2 days when they get purged by other nodes.
Ravi Ojha
CC BY-SA 4.0
2023-11-21T10:07:09.047Z
2023-11-21T10:07:09.047Z
dev7ba
<p>I'm running a fullnode with electrumx on top for indexing. I've noticed that sometimes, due to low fee, a tx gets dropped from mempool after some hours/days. However, it stays for longer periods in my node. Here's bitcoind config.</p>
<pre><code>daemon=1
server=1
txindex=1
listen=1
maxmempool=350
mempoolexpiry=48
mempoolfullrbf=1
maxconnections=42
minrelaytxfee=0.00001
</code></pre>
<p>Here <code>mempoolexpiry</code> is set as <code>48</code>. Is this what's preventing that txn from getting dropped for two days even though it's already dropped from other mempools? What would be an ideal number for this parameter?</p>

CC BY-SA 4.0
2023-11-13T08:48:51.883Z
What mempool are you comparing to? Do you mean [mempool.space](https://mempool.space/)?
Vojtěch Strnad
CC BY-SA 4.0
2023-11-13T11:49:22.453Z
@VojtěchStrnad I checked in 3 explorers. mempool.space, blockstream, blockchair. They all say tx not found.
Ravi Ojha
CC BY-SA 4.0
2023-11-21T18:45:09.167Z
Okay, so purging txn below certain feerate is what seems to be causing this problem. Other nodes are probably purging aggressively. While my node keeps that txn for 2 days before dropping them.
Ravi Ojha
CC BY-SA 4.0
2023-11-21T18:47:38.740Z
As far as I know, mempool.space never purges transactions and has its mempool capped at 2 GB, so if it doesn't have your transaction it's more likely that it never propagated to it through the network.
Vojtěch Strnad
CC BY-SA 4.0
2023-11-21T18:54:06.280Z
I see. Would you know what it means on their home page `Purging < 9.85 sat/vB`
Ravi Ojha
CC BY-SA 4.0
2023-11-21T21:50:21.453Z
That refers to the default mempool of 300 MB. Transactions below that fee rate don't propagate through most nodes.
Vojtěch Strnad
<bitcoin-core><bitcoind><unconfirmed-transactions><mempool>
How to remove a tx from local node mempool that's been removed from all other node
Ravi Ojha
# How to remove a tx from local node mempool that's been removed from all other node

(Asked by: username_0 on 2023-11-13)

I'm running a fullnode with electrumx on top for indexing. I've noticed that sometimes, due to low fee, a tx gets dropped from mempool after some hours/days. However, it stays for longer periods in my node. Here's bitcoind config.

```
daemon=1
server=1
txindex=1
listen=1
maxmempool=350
mempoolexpiry=48
mempoolfullrbf=1
maxconnections=42
minrelaytxfee=0.00001

```

Here `mempoolexpiry` is set as `48`. Is this what's preventing that txn from getting dropped for two days even though it's already dropped from other mempools? What would be an ideal number for this parameter?

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

> **Comments:**
> **username_1**: What mempool are you comparing to? Do you mean [mempool.space](https://mempool.space/)?  
> **username_0**: @username_1 I checked in 3 explorers. mempool.space, blockstream, blockchair. They all say tx not found.  
> **username_0**: Okay, so purging txn below certain feerate is what seems to be causing this problem. Other nodes are probably purging aggressively. While my node keeps that txn for 2 days before dropping them.  
> **username_1**: As far as I know, mempool.space never purges transactions and has its mempool capped at 2 GB, so if it doesn't have your transaction it's more likely that it never propagated to it through the network.  
> **username_0**: I see. Would you know what it means on their home page `Purging < 9.85 sat/vB`  
> **username_1**: That refers to the default mempool of 300 MB. Transactions below that fee rate don't propagate through most nodes.  

---

## 1 answers

### Answer by username_2 on 2023-11-21. Score: 1

Default value for mempoolexpiry is 336. That is two weeks. Your value is 48 so that means that a transaction in your mempool for more than 2 days will be dropped. I consider that value to be inappropriate (too low) given the current mempool size (+300 blocks). Is there any reason for that value in your node?

Also, any node do not (re)transmit txs that are already on the mempoool. That is a anti-spam measurement. It's possible that you received the transaction when you were starting your node (poorly connected) by another starting node also poorly connected, so that transaction got stuck in both mempools. Also the agent (maybe yourself) that send the transaction in first place has not re-transmitted the transaction since then.

There is no way to remove that tx from your mempool but you can rebroadcast it again by other means (i.e. <https://bitaccelerate.com/pushtx/>) and wait to be mined.

I've also found that my node (which feeds my webpage <https://mempoolexplorer.com>) sometimes has transactions that any other service have. Maybe for the same reason.

> **Comments:**
> **username_0**: 2 days works for our specific usecase. If the txn is indeed mined after a week, it will be synced anyway as part of new block data. So this hasn't caused any problems.  In fact, I'm looking at a way to drop (or purge) txns even before 2 days when they get purged by other nodes.  

---

