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?
3
-
Are all of the miners doing their getwork() requests from the same instance of bitcoind?– David PerryOct 10, 2012 at 3:18
-
1The 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 GornickOct 10, 2012 at 5:05
-
Sorry for not being clear; this question was purely theoretical. @DavidPerry Yes, as if I'm operating a pool just for myself.– ConstableJoeOct 10, 2012 at 17:57
Add a comment
|
2 Answers
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.
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.
answered Oct 10, 2012 at 6:55
-
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. Oct 10, 2012 at 8:48