|
May 23, 2013, 11:19:12 PM |
|
Hopefully someone can explain why this wouldn't work, I can't be the first person to think of this.
Say I have an account on two different pools worker: scrubadub.1 on pool A and worker: scrubadub.2 on pool B
Let's say I can set the var diff manually on both so I set... scrubadub.1 to vardiff 64 and scrubadub.2 to vardiff 32
Now I start mining.
If I get a share above 64 I submit it to worker scrubadub.1. That pool accepts it and also credits me for the expected amount of shares under 64 that I would've also found (and not submitted) depending on the rate of shares that I submit above 64. If we stop here I would get credited for roughly 100% of the shares I find (with a little variance)
But, while I'm still mining if I find a share between 32 and 63 instead of just dropping it I instead submit it to scrubadub.2. That pool accepts it and credits me for that share and the expected number of shares I would've also solved below 32 given the rate that I submit above 32.
At the end of the day I ended up with a much larger credit of shares than I actually solved. Pool A can't see any difference in the way I submit shares, Pool B could if I'm so clear cut about it, but you could get more random in what you submit.
So I guess my question is can I locally generate my own work or am I forced to solve the work from the pools (which would prevent this). Looking at my cgminer output for locally generated work (LW:) it seems quite high, but I'm not sure how many "locally generated work" are required before a share is found.
Thoughts?
|