<blockquote>
  <p>Do they just get rejected?</p>
</blockquote>

<p>No, they will just wait for another block to be included in.</p>

<p>Note that transactions have a time to live in the mempool of 336 hours (configurable using the <code>maxmempoolexpiry</code> startup option). </p>

CC BY-SA 4.0
2020-04-24T07:33:56.360Z
2020-04-24T07:33:56.360Z
Antoine Poinsot
<p>Addition to darosior's answer:</p>

<p>Remember that there's no single mempool - every node maintains its own. Thus a miner can mine a transaction after a long time if it's still valid (its input not spent by another transaction.)</p>

CC BY-SA 4.0
2020-04-24T07:35:52.677Z
2020-04-24T07:35:52.677Z
MCCCS
<p>When bitcoin transactions are made, I know that they are put into the mempool. After certain transactions are added to a block and that block gets verified, what happens to all the other transactions that did not meet that threshold? Do they just get rejected?</p>

<unconfirmed-transactions><mempool>
Question about transactions added to mempool
tteo57
# Question about transactions added to mempool

(Asked by: username_0 on 2020-04-24)

When bitcoin transactions are made, I know that they are put into the mempool. After certain transactions are added to a block and that block gets verified, what happens to all the other transactions that did not meet that threshold? Do they just get rejected?

**Tags:** unconfirmed-transactions, mempool


---

## 2 answers

### Answer by username_1 on 2020-04-24. Score: 3 | Accepted answer

> Do they just get rejected?

No, they will just wait for another block to be included in.

Note that transactions have a time to live in the mempool of 336 hours (configurable using the `maxmempoolexpiry` startup option).


---

### Answer by username_2 on 2020-04-24. Score: 1

Addition to darosior's answer:

Remember that there's no single mempool - every node maintains its own. Thus a miner can mine a transaction after a long time if it's still valid (its input not spent by another transaction.)


---

