<p>There's several factors at play, one of them is that the underlying implementation of the Stratum protocol on many miners. Due to the way they are implemented many miners will drop a connection with their pool if they have not seen any updates in 30 seconds, as a result most pools will push work updates at this frequency. </p>

<p>Optimally, mining pools would update their work based on the block reward rather than a fixed timer. If the fee amount in their template has not moved it is not optimal for them to push new work, but if it has increased by a substantial monetary value it is optimal for them to push new work regardless of how recent the last update was. </p>

<hr>

<p>Historically restarting work took a long time, but modern ASICs tend to take hundreds of milliseconds to alter the work they are performing, whereas older miners like HashFast could take tens of seconds. </p>

CC BY-SA 4.0
2018-09-29T13:08:16.650Z
2018-09-29T13:08:16.650Z
Claris
<p>I realize that this is a general question with no "correct" answer, as every miner can operate differently.</p>

<p>Having said that, I'd like to be able to display a list of transactions that would be considered <strong>a <em>fair</em> representation of the transactions in the memory pool that are poised to be mined</strong>.</p>

<p>So far I have been:</p>

<ul>
<li>Using <code>getblocktemplate</code> to get the list of transactions.</li>
<li>Refreshing the list when a new block arrives, or at <strong>1 minute intervals</strong>.</li>
</ul>

<hr>

<p>Using <code>getblocktemplate</code> seems logical, as I imagine the majority of miners would like to get the most amount possible in fees from their blocks.</p>

<p>I'm then guessing that miners would want to refresh their candidate block at certain intervals to check for higher-fee transactions in the mempool.</p>

<p>Is it likely that miners would be inclined to refresh their candidate blocks much more (or less) than every minute?</p>

<mining-profitability><mining-theory>
How often does a typical miner refresh their candidate block?
inersha
# How often does a typical miner refresh their candidate block?

(Asked by: username_0 on 2016-12-02)

I realize that this is a general question with no "correct" answer, as every miner can operate differently.

Having said that, I'd like to be able to display a list of transactions that would be considered **a *fair* representation of the transactions in the memory pool that are poised to be mined**.

So far I have been:

* Using `getblocktemplate` to get the list of transactions.
* Refreshing the list when a new block arrives, or at **1 minute intervals**.

---

Using `getblocktemplate` seems logical, as I imagine the majority of miners would like to get the most amount possible in fees from their blocks.

I'm then guessing that miners would want to refresh their candidate block at certain intervals to check for higher-fee transactions in the mempool.

Is it likely that miners would be inclined to refresh their candidate blocks much more (or less) than every minute?

**Tags:** mining-profitability, mining-theory


---

## 1 answers

### Answer by username_1 on 2018-09-29. Score: 1

There's several factors at play, one of them is that the underlying implementation of the Stratum protocol on many miners. Due to the way they are implemented many miners will drop a connection with their pool if they have not seen any updates in 30 seconds, as a result most pools will push work updates at this frequency.

Optimally, mining pools would update their work based on the block reward rather than a fixed timer. If the fee amount in their template has not moved it is not optimal for them to push new work, but if it has increased by a substantial monetary value it is optimal for them to push new work regardless of how recent the last update was.

---

Historically restarting work took a long time, but modern ASICs tend to take hundreds of milliseconds to alter the work they are performing, whereas older miners like HashFast could take tens of seconds.


---

