<blockquote>
<p>Im gonna cover from 0 to 500, and you cover from 500 to 1000, then if nobody find it we up 500 more</p>
</blockquote>
<p>Yes, <a href="https://github.com/aeternity/protocol/blob/master/STRATUM.md#response" rel="nofollow noreferrer">the server coordinates this</a>:</p>
<blockquote>
<p>The server SHOULD assign disjoint subspaces of the 8 byte nonce space to miners, avoiding the problem of multiple miners working on the same problem.</p>
</blockquote>
<blockquote>
<p>And if they do use range does they tell it to other mining pool, so that they are not searching around the same number ?</p>
</blockquote>
<p>No, instead, usually coinbase tx contains the pool name which guarantees separate search spaces. <strong>EDIT</strong>: This is not needed since the payout address is different already (thanks, Pieter Wuille)</p>

CC BY-SA 4.0
2021-01-08T19:58:39.707Z
It doesn't need the pool name; you can mine anonymously. But at the very least, the payout address of one miner won't match that of another (they want to pay themselves!), so the coinbase tx will never collide.
Pieter Wuille
CC BY-SA 4.0
2021-01-08T19:36:54.747Z
2021-01-08T20:08:14.807Z
2021-01-08T20:08:14.807Z
MCCCS
<p>Most mining pools use the stratum protocol. Part of this protocol includes a field for part of the extraNonce, named <code>extraNonce1</code>. The extraNonce is just extra data that is put in the coinbase transaction and used as a nonce in addition to the block's nonce. Each mining worker can then append their own extraNonce to <code>extraNonce1</code>. This second part is named <code>extraNonce2</code></p>
<p>Typically what mining pools do is they issue work to each worker with a different <code>extraNonce1</code>. This allows the worker to use the entirety of the nonce field as well as their own space for <code>extraNonce2</code>. The submitted work can also be identified to belong to a particular worker by examining the <code>extraNonce1</code>.</p>
<p>I'm not sure how specific mining pool software determine what <code>extraNonce1</code> to give out, but an obvious method would be to do so sequentially - each time work is issued, <code>extraNonce1</code> is incremented so that each worker gets something different to work on.</p>

CC BY-SA 4.0
2021-01-08T20:16:48.897Z
It's just randomly assigned. There's no point in trying to make any of this sequential, as it would require pool servers to coordinate unnecessarily.
Claris
CC BY-SA 4.0
2021-01-08T19:37:16.957Z
2021-01-08T19:37:16.957Z
Ava Chow
<p>When it comes to hashing does each mining entity use total random seed for each of their hashing function or do they have a range like &quot; Im gonna cover from 0 to 500, and you cover from 500 to 1000, then if nobody find it we up 500 more &quot;</p>
<p>And if they do use range does they tell it to other mining pool, so that they are not searching around the same number ?</p>

<mining-pools><mining-theory><block><hash>
Does bitcoin mining pool hash randomly and separately
Saxtheowl
# Does bitcoin mining pool hash randomly and separately

(Asked by: username_0 on 2021-01-08)

When it comes to hashing does each mining entity use total random seed for each of their hashing function or do they have a range like " Im gonna cover from 0 to 500, and you cover from 500 to 1000, then if nobody find it we up 500 more "

And if they do use range does they tell it to other mining pool, so that they are not searching around the same number ?

**Tags:** mining-pools, mining-theory, block, hash


---

## 2 answers

### Answer by username_3 on 2021-01-08. Score: 5 | Accepted answer

Most mining pools use the stratum protocol. Part of this protocol includes a field for part of the extraNonce, named `extraNonce1`. The extraNonce is just extra data that is put in the coinbase transaction and used as a nonce in addition to the block's nonce. Each mining worker can then append their own extraNonce to `extraNonce1`. This second part is named `extraNonce2`

Typically what mining pools do is they issue work to each worker with a different `extraNonce1`. This allows the worker to use the entirety of the nonce field as well as their own space for `extraNonce2`. The submitted work can also be identified to belong to a particular worker by examining the `extraNonce1`.

I'm not sure how specific mining pool software determine what `extraNonce1` to give out, but an obvious method would be to do so sequentially - each time work is issued, `extraNonce1` is incremented so that each worker gets something different to work on.

> **Comments:**
> **username_4**: It's just randomly assigned. There's no point in trying to make any of this sequential, as it would require pool servers to coordinate unnecessarily.  

---

### Answer by username_1 on 2021-01-08. Score: 0

> Im gonna cover from 0 to 500, and you cover from 500 to 1000, then if nobody find it we up 500 more

Yes, [the server coordinates this](https://github.com/aeternity/protocol/blob/master/STRATUM.md#response):

> The server SHOULD assign disjoint subspaces of the 8 byte nonce space to miners, avoiding the problem of multiple miners working on the same problem.

> And if they do use range does they tell it to other mining pool, so that they are not searching around the same number ?

No, instead, usually coinbase tx contains the pool name which guarantees separate search spaces. **EDIT**: This is not needed since the payout address is different already (thanks, username_2 username_2)

> **Comments:**
> **username_2**: It doesn't need the pool name; you can mine anonymously. But at the very least, the payout address of one miner won't match that of another (they want to pay themselves!), so the coinbase tx will never collide.  

---

