<p>Blocks commit to the set of transactions they contain, including the coinbase transaction. The coinbase transaction is the transaction which pays the subsidy/fees out to the miner who mined it.</p>
<p>Since every miner pays themselves in the blocks they're trying to construct, no two miners will ever attempt to build blocks that have identical coinbase transactions.</p>

CC BY-SA 4.0
2022-05-18T16:17:09.017Z
People often forget that the block "needs to know" who should receive the minted coin.
Mindwin Remember Monica
CC BY-SA 4.0
2022-05-19T09:36:19.650Z
Is this the case for clients inside a mining pool as well?
Taemyr
CC BY-SA 4.0
2022-05-19T10:59:41.380Z
@Taemyr, pool must give clients different seed, otherwise will be inefficient.
akostadinov
CC BY-SA 4.0
2022-05-19T15:55:27.113Z
Yeah, in a pool the pool operator will assign different (sets of) coinbase transactions to different hashers. The pool must make sure that no two hashers ever work on the same problem, as that'd be duplicate work.
Pieter Wuille
CC BY-SA 4.0
2022-05-18T16:08:01.000Z
2022-05-18T19:52:16.333Z
2022-05-18T19:52:16.333Z
Pieter Wuille
<p>How does the mining clients make sure that the seeds are not the exact same computed on every mining rig in the world with for example a GTX 1080 with the same speed? So that it is not the quickest miner that gets the reward.</p>
<p>For example. Seeds: 0xA, 0xB, 0xC, 0xD etc...</p>
<p>Is the seeds for computing hash just a counter up from 0? Or is the seeds for the hash totally random?</p>

CC BY-SA 4.0
2022-05-20T07:32:15.187Z
Effectively dupe https://bitcoin.stackexchange.com/questions/113195/using-prng-to-get-better-mining-results
dave_thompson_085
<mining-theory><hash><miner-configuration>
How is mining the exact same hash on every computer avoided?
Henning
# How is mining the exact same hash on every computer avoided?

(Asked by: username_0 on 2022-05-18)

How does the mining clients make sure that the seeds are not the exact same computed on every mining rig in the world with for example a GTX 1080 with the same speed? So that it is not the quickest miner that gets the reward.

For example. Seeds: 0xA, 0xB, 0xC, 0xD etc...

Is the seeds for computing hash just a counter up from 0? Or is the seeds for the hash totally random?

**Tags:** mining-theory, hash, miner-configuration

> **Comments:**
> **username_1**: Effectively dupe https://bitcoin.stackexchange.com/questions/113195/using-prng-to-get-better-mining-results  

---

## 1 answers

### Answer by username_2 on 2022-05-18. Score: 11

Blocks commit to the set of transactions they contain, including the coinbase transaction. The coinbase transaction is the transaction which pays the subsidy/fees out to the miner who mined it.

Since every miner pays themselves in the blocks they're trying to construct, no two miners will ever attempt to build blocks that have identical coinbase transactions.

> **Comments:**
> **username_3**: People often forget that the block "needs to know" who should receive the minted coin.  
> **username_4**: Is this the case for clients inside a mining pool as well?  
> **username_5**: @username_4, pool must give clients different seed, otherwise will be inefficient.  
> **username_2**: Yeah, in a pool the pool operator will assign different (sets of) coinbase transactions to different hashers. The pool must make sure that no two hashers ever work on the same problem, as that'd be duplicate work.  

---

