<p>Bitcoind will of course give different data to each of the miners connecting to it. Otherwise using multiple miners would be pointless.</p>

<p>It needn't necessarily give a different <em>address</em> (though normally it does) - it's enough to change the extraNonce field.</p>

CC BY-SA 3.0
2012-10-10T05:46:10.333Z
2012-10-10T05:46:10.333Z
Meni Rosenfeld
<p>It really does not matter. The nature of mining is random. Whether you will use different addresses or the same one, your hashing will be different from the other people's hashing. As long as an identical work is not assigned to two people (both in term of nonces and merkle root), the results will be the same.</p>

CC BY-SA 3.0
2012-10-10T08:48:00.400Z
But typically the normal transactions will be the same (whatever is known at the time), and all nonce values are tried sequentially. The only thing that is reliably random between miners is the generation transaction, meaning the extraNonce and reward address.
Meni Rosenfeld
CC BY-SA 3.0
2012-10-10T06:55:43.183Z
2012-10-15T02:18:47.930Z
2012-10-15T02:18:47.930Z
ThePiachu
<p>I've heard that what prevents the fastest computers from almost always dominating pools is that each miner is hashing different data because of the generation transaction. However, if I solo mine with many of my own computers running miners connecting to a bitcoind I'm running, it seems like I'm going to redo the same work across all miners because the generation transaction address would be the same. Or should each miner have its own address? Or should bitcoind generate a new address for each getwork request?</p>

CC BY-SA 3.0
2012-10-10T03:18:42.133Z
Are all of the miners doing their getwork() requests from the same instance of bitcoind?
David Perry
CC BY-SA 3.0
2012-10-10T05:05:12.803Z
The threshold where solo mining doesn't make sense is currently anything below tens of GHashs/s.  Perhaps nearing 100 Ghash/s soon.  Are you sure you want to solo mine?
Stephen Gornick
CC BY-SA 3.0
2012-10-10T17:57:42.927Z
Sorry for not being clear; this question was purely theoretical.

@DavidPerry Yes, as if I'm operating a pool just for myself.
ConstableJoe
<mining-pools><solo-mining>
Does solo mining with multiple computers require different generation transaction addresses?
ConstableJoe
# Does solo mining with multiple computers require different generation transaction addresses?

(Asked by: username_0 on 2012-10-10)

I've heard that what prevents the fastest computers from almost always dominating pools is that each miner is hashing different data because of the generation transaction. However, if I solo mine with many of my own computers running miners connecting to a bitcoind I'm running, it seems like I'm going to redo the same work across all miners because the generation transaction address would be the same. Or should each miner have its own address? Or should bitcoind generate a new address for each getwork request?

**Tags:** mining-pools, solo-mining

> **Comments:**
> **username_1**: Are all of the miners doing their getwork() requests from the same instance of bitcoind?  
> **username_2**: The threshold where solo mining doesn't make sense is currently anything below tens of GHashs/s.  Perhaps nearing 100 Ghash/s soon.  Are you sure you want to solo mine?  
> **username_0**: Sorry for not being clear; this question was purely theoretical.  @username_1 Yes, as if I'm operating a pool just for myself.  

---

## 2 answers

### Answer by username_3 on 2012-10-10. Score: 3 | Accepted answer

Bitcoind will of course give different data to each of the miners connecting to it. Otherwise using multiple miners would be pointless.

It needn't necessarily give a different *address* (though normally it does) - it's enough to change the extraNonce field.


---

### Answer by username_4 on 2012-10-10. Score: 0

It really does not matter. The nature of mining is random. Whether you will use different addresses or the same one, your hashing will be different from the other people's hashing. As long as an identical work is not assigned to two people (both in term of nonces and merkle root), the results will be the same.

> **Comments:**
> **username_3**: But typically the normal transactions will be the same (whatever is known at the time), and all nonce values are tried sequentially. The only thing that is reliably random between miners is the generation transaction, meaning the extraNonce and reward address.  

---

