<p>Basically, you can include whichever transactions you'd like.</p>

<p>Currently most miners simply include all valid transactions they know of. It is cheap to do so.</p>

<p>There is currently a limit of 1 MB per block, so as transaction volume reaches these levels, miners will typically want to include transactions that have the best ratio of fee / data size.</p>

<p>As a more mature transaction fee framework evolves, miners will choose transactions to optimize for it.</p>

<p>Playing with transactions included is not needed to extend your work scope, as you can extend it indefinitely by changing the extraNonce.</p>

CC BY-SA 3.0
2013-08-27T13:36:16.603Z
2013-08-27T13:42:16.297Z
2013-08-27T13:42:16.297Z
Meni Rosenfeld
<p>I saw <a href="https://bitcoin.stackexchange.com/questions/1725/how-to-know-there-is-a-new-transaction">this question</a> about finding new transactions.</p>

<p>But how do you pick which transactions to include in the block you're trying to add? Should it be in a certain order, or random? How many transactions should you include? Looking at the blockchain I've seen anywhere from just a few, to hundreds. Is the number of transactions something you'd vary when pool-mining to combat exhausting all possible nonces if up-to-date with the timestamp header? (Loosely related to my other recent questions).</p>

<transactions><mining-pools><block><transaction-selection>
How to 'pick' transactions to include when attempting to add a new block?
Anonymous
# How to 'pick' transactions to include when attempting to add a new block?

(Asked by: username_0 on 2013-08-27)

I saw [this question](https://bitcoin.stackexchange.com/questions/1725/how-to-know-there-is-a-new-transaction) about finding new transactions.

But how do you pick which transactions to include in the block you're trying to add? Should it be in a certain order, or random? How many transactions should you include? Looking at the blockchain I've seen anywhere from just a few, to hundreds. Is the number of transactions something you'd vary when pool-mining to combat exhausting all possible nonces if up-to-date with the timestamp header? (Loosely related to my other recent questions).

**Tags:** transactions, mining-pools, block, transaction-selection


---

## 1 answers

### Answer by username_1 on 2013-08-27. Score: 5 | Accepted answer

Basically, you can include whichever transactions you'd like.

Currently most miners simply include all valid transactions they know of. It is cheap to do so.

There is currently a limit of 1 MB per block, so as transaction volume reaches these levels, miners will typically want to include transactions that have the best ratio of fee / data size.

As a more mature transaction fee framework evolves, miners will choose transactions to optimize for it.

Playing with transactions included is not needed to extend your work scope, as you can extend it indefinitely by changing the extraNonce.


---

