<p>There's no relationship. With a single block template mining software can create a limitless amount of work by modifying the extranonce, the only reason they would need to update to a new one is to include transactions that have just arrived, or when someone else has found a block. The reason <code>GetWork</code> rates varied was that each request was only valid for a single 2**32 nonce range, which a modern ASIC miner can exhaust in milliseconds. </p>

CC BY-SA 3.0
2015-06-17T06:10:45.690Z
2015-06-17T06:10:45.690Z
Claris
<p>What is the relationship between a miner's hashrate and the <a href="https://en.bitcoin.it/wiki/Getblocktemplate" rel="nofollow noreferrer">getblocktemplate (GBT)</a> request rate?</p>

<p><sup>(The question here, "<a href="https://bitcoin.stackexchange.com/q/3427/4334">How does the rate of getwork requests correlate with the hashrate of a miner?</a>," discusses <a href="https://en.bitcoin.it/wiki/Getwork" rel="nofollow noreferrer">getwork</a>, but that's outdated.)</sup></p>

<mining-pools><hashpower><getblocktemplate>
How does the getblocktemplate request rate correlate with a miner's hashrate?
Geremia
# How does the getblocktemplate request rate correlate with a miner's hashrate?

(Asked by: username_0 on 2015-06-16)

What is the relationship between a miner's hashrate and the [getblocktemplate (GBT)](https://en.bitcoin.it/wiki/Getblocktemplate) request rate?

(The question here, "[How does the rate of getwork requests correlate with the hashrate of a miner?](https://bitcoin.stackexchange.com/q/3427/4334)," discusses [getwork](https://en.bitcoin.it/wiki/Getwork), but that's outdated.)

**Tags:** mining-pools, hashpower, getblocktemplate


---

## 1 answers

### Answer by username_1 on 2015-06-17. Score: 1 | Accepted answer

There's no relationship. With a single block template mining software can create a limitless amount of work by modifying the extranonce, the only reason they would need to update to a new one is to include transactions that have just arrived, or when someone else has found a block. The reason `GetWork` rates varied was that each request was only valid for a single 2\*\*32 nonce range, which a modern ASIC miner can exhaust in milliseconds.


---

