4

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?

1

1 Answer 1

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.

4
  • 3
    People often forget that the block "needs to know" who should receive the minted coin.
    – Mindwin
    May 18 at 16:17
  • 1
    Is this the case for clients inside a mining pool as well?
    – Taemyr
    May 19 at 9:36
  • @Taemyr, pool must give clients different seed, otherwise will be inefficient. May 19 at 10:59
  • 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. May 19 at 15:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.