With walletaddress/10000000 one share is worth ~0.009 or 500ghs/day in grahps, bigger hook can give you bigger fish. And no its not high
OK I am not sure I understand... Is it more beneficial to use this?? 10000000 or not?
Thanks for any info on this.... and will it be any help to the S2's in use?
I'm not sure what help, if any, it would be for the S2.
Setting the difficulty manually like this tells the p2pool node that you are hashing on not to dynamically assign you a share difficulty, but to use the value you provide instead. So, if the current share difficulty for getting a share onto the chain is 2000000, and you set your difficulty to 10000000, any shares you happen to find greater than 2000000 but less than 10000000 are not added to the chain. It isn't until your miner finds a share at your difficulty that it would be added to the chain. Because your share difficulty is set higher than the pool's default, when you find that 10000000 share, it is weighted heavier (meaning worth more BTC).
I honestly don't know what kind of benefit this would offer you other than creating a higher variance. I mean, unless you've got enough hashing power such that you're finding shares faster than every 30 seconds, what's the point of slowing down the rate at which you find a share?
IMHO it doesn't do a thing. It doesn't even affect variance, as you still need a share worth 2m to get on the share chain.
You can't find a share faster than every 30 seconds. That's why the difficulty adjusts ... to make sure the average time per share is 30 seconds. That's why if we change it to 2 minutes, the share difficulty has to increase, otherwise folks will still find shares approx ~30 seconds.
I never had any visible result from using /xxxxx, just +xxxx. Plus I know p2pool has some odd arbitrary upper limits on what values you can put there.
M
.