<p>No, there's not a need. The "work" generated by the pool includes the time, transactions, transaction order, and a completely unique coinbase. All of this information is hashed once with SHA256 and then sent to the client for them to do the POW calculation on. There is absolutely no chance of two pools creating the same work, and indeed pool software is designed to make work unique to each user. Protocols like GBT and Stratum also generate work items locally so the pool server is even less involved. </p>

CC BY-SA 3.0
2013-12-08T23:52:16.803Z
How does the pool make the coinbase unique?
RentFree
CC BY-SA 3.0
2013-12-08T23:56:21.543Z
The coinbase is largely random, it needs to be otherwise the block could contain a non-unique transaction ID, which would make the block invalid and useless. At the present time the `coinbase` often contains information like a vote, the name of the pool, or merged mining information. Block #212261's coinbase decodes to "#= BitMinter/P2SH/,ú¾mmÏ�|ì�i§[Ð³\�e?3w�&ý �¶ù (¨ÇÎñÕ eu1º*" for example, which indicates the pool "bitminter" and a lot of random padding. Not all coinbases decode to human readable, a lot are just left totally random.
Anonymous
CC BY-SA 3.0
2013-12-09T02:28:19.590Z
Perhap you could add to your answer how the pool software makes the work unique to each user?
Highly Irregular
CC BY-SA 3.0
2014-04-28T15:35:48.093Z
This does not answer the question.  You are answering the question of "how do 2 different POOLS make sure they're not doing the same work".  My question was "how does an individual POOL make sure no 2 pool MEMBERS are doing the same work"
RentFree
CC BY-SA 4.0
2020-01-26T07:58:24.007Z
@RentFree "and a completely unique coinbase".
David Schwartz
CC BY-SA 3.0
2013-12-08T23:49:59.463Z
2013-12-08T23:49:59.463Z
Anonymous
<p>Do mining pools take any precautions to make sure that their members are not doing the exact same work (i.e. they've been given the exact same block to mine, and thus they're doing the same hash calculations as a fellow member)?</p>

CC BY-SA 3.0
2014-04-28T16:17:03.497Z
Possible duplicate: [How do mining pools distribute work effectively?](http://bitcoin.stackexchange.com/q/12955/5406)
Murch
<mining-pools>
How do mining-pools prevent work duplication?
RentFree
# How do mining-pools prevent work duplication?

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

Do mining pools take any precautions to make sure that their members are not doing the exact same work (i.e. they've been given the exact same block to mine, and thus they're doing the same hash calculations as a fellow member)?

**Tags:** mining-pools

> **Comments:**
> **username_1**: Possible duplicate: [How do mining pools distribute work effectively?](http://bitcoin.stackexchange.com/q/12955/5406)  

---

## 1 answers

### Answer by username_2 on 2013-12-08. Score: 2

No, there's not a need. The "work" generated by the pool includes the time, transactions, transaction order, and a completely unique coinbase. All of this information is hashed once with SHA256 and then sent to the client for them to do the POW calculation on. There is absolutely no chance of two pools creating the same work, and indeed pool software is designed to make work unique to each user. Protocols like GBT and Stratum also generate work items locally so the pool server is even less involved.

> **Comments:**
> **username_0**: How does the pool make the coinbase unique?  
> **username_2**: The coinbase is largely random, it needs to be otherwise the block could contain a non-unique transaction ID, which would make the block invalid and useless. At the present time the `coinbase` often contains information like a vote, the name of the pool, or merged mining information. Block #212261's coinbase decodes to "#= BitMinter/P2SH/,ú¾mmÏ�|ì�i§[Ð³\�e?3w�&ý �¶ù (¨ÇÎñÕ eu1º*" for example, which indicates the pool "bitminter" and a lot of random padding. Not all coinbases decode to human readable, a lot are just left totally random.  
> **username_3**: Perhap you could add to your answer how the pool software makes the work unique to each user?  
> **username_0**: This does not answer the question.  You are answering the question of "how do 2 different POOLS make sure they're not doing the same work".  My question was "how does an individual POOL make sure no 2 pool MEMBERS are doing the same work"  
> **username_4**: @username_0 "and a completely unique coinbase".  

---

