<p>Hash rate measures how fast your miner can attempt to find a nonce that satisfies the proof of work.  The speed at which it performs this task is not related to network bandwidth.  It does not perform a network operation <em>per hash</em>.</p>

<p>Bitcoin mining still requires network usage, however.  Your miner will request a unit of work from the mining pool, which is really just a block header.  This is only 608 bits (not bytes) of data.  Your miner's job is to fill in the remaining 32 bits of the block header (total size is 640 bits), called the "nonce", and hash it to determine if the proof of work is satisfied.  If you have exhausted all 2^32 options, then you will request a new unit of work.</p>

<p>So your miner will request units of work more often the faster it can hash, but this amount of network traffic is small.  Since each unit of work is only 608 bits, this is a very negligible bandwidth usage.  You won't see a significant increase in profitability by increasing bandwidth.</p>

<p>You may want to check out <a href="https://bitcoin.stackexchange.com/a/12962/24974">this answer</a> to <a href="https://bitcoin.stackexchange.com/questions/12955/how-do-mining-pools-distribute-work-effectively">How do mining pools distribute work effectively?</a>, specifically the comments.</p>

CC BY-SA 3.0
2016-07-07T15:06:30.227Z
forgive my confusion, I'm familiar with distributed super computing but Im brand new to bitcoin. I think my router has a traffic analyzer I can use for an exact figure.
j0h
CC BY-SA 3.0
2016-07-07T15:08:41.383Z
That would be cool.  Remember that it's not just the 608 bytes, but also the overhead of the mining pool protocol.  I just wanted to make sure you didn't think that the network is required for each hash.  That would be a *lot* of traffic :)
Jestin
CC BY-SA 3.0
2016-07-08T12:00:25.023Z
Presumably, as discussed in the answer you link, modern pools don't actually require a separate request for every block header.  Otherwise a modern multi-terahash miner would be totally bogged down by the latency.
Nate Eldredge
CC BY-SA 3.0
2016-07-07T14:01:13.217Z
2016-07-07T14:01:13.217Z
2017-04-13T12:47:36.647Z
Jestin
<p>What is the relationship between bandwidth and hash rate?
I have an AntMiner S4 mining at 2.1GHashes.
I understand that the miner has no hard drive, and does its operations purely in memory, and that the device sends and receives data when calculations are complete. </p>

<p>My question is what does running a Bitcoin Miner do to network load (I am assuming network load is a function of Hash rate). </p>

CC BY-SA 3.0
2016-07-07T21:34:26.603Z
There is very little connection between network load and hash rate.
David Schwartz
<hashpower><bandwidth>
what is the relationship between bandwidth and hash rate?
j0h
# what is the relationship between bandwidth and hash rate?

(Asked by: username_0 on 2016-07-07)

What is the relationship between bandwidth and hash rate?
I have an AntMiner S4 mining at 2.1GHashes.
I understand that the miner has no hard drive, and does its operations purely in memory, and that the device sends and receives data when calculations are complete.

My question is what does running a Bitcoin Miner do to network load (I am assuming network load is a function of Hash rate).

**Tags:** hashpower, bandwidth

> **Comments:**
> **username_1**: There is very little connection between network load and hash rate.  

---

## 1 answers

### Answer by username_2 on 2016-07-07. Score: 2 | Accepted answer

Hash rate measures how fast your miner can attempt to find a nonce that satisfies the proof of work. The speed at which it performs this task is not related to network bandwidth. It does not perform a network operation *per hash*.

Bitcoin mining still requires network usage, however. Your miner will request a unit of work from the mining pool, which is really just a block header. This is only 608 bits (not bytes) of data. Your miner's job is to fill in the remaining 32 bits of the block header (total size is 640 bits), called the "nonce", and hash it to determine if the proof of work is satisfied. If you have exhausted all 2^32 options, then you will request a new unit of work.

So your miner will request units of work more often the faster it can hash, but this amount of network traffic is small. Since each unit of work is only 608 bits, this is a very negligible bandwidth usage. You won't see a significant increase in profitability by increasing bandwidth.

You may want to check out [this answer](https://bitcoin.stackexchange.com/a/12962/24974) to [How do mining pools distribute work effectively?](https://bitcoin.stackexchange.com/questions/12955/how-do-mining-pools-distribute-work-effectively), specifically the comments.

> **Comments:**
> **username_0**: forgive my confusion, I'm familiar with distributed super computing but Im brand new to bitcoin. I think my router has a traffic analyzer I can use for an exact figure.  
> **username_2**: That would be cool.  Remember that it's not just the 608 bytes, but also the overhead of the mining pool protocol.  I just wanted to make sure you didn't think that the network is required for each hash.  That would be a *lot* of traffic :)  
> **username_3**: Presumably, as discussed in the answer you link, modern pools don't actually require a separate request for every block header.  Otherwise a modern multi-terahash miner would be totally bogged down by the latency.  

---

