Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

couple of questions
1. is 0.00000116 a static constant, or based off dynamic number?  Wondering if i need to redo the math periodically to keep my miners running efficiently.
2. do you know of any downsides to restarting p2pool, i noticed i lost a few shares once i had done so, but technically i dont understand why that would be.  i did however update the -a payout address, perhaps that restages the pool?
3. "expected time to share" seems to stay around 7-12hrs, im assuming its because the pool doesn't have any stats to work off of yet?
4. "payout if a block were found NOW" seems to remain at 0, any tips on that?
5. know of any p2pool advanced docs/manuals out there?

Thanks for any info

I'm showing 682TH/s on my node, a nice jump....

If you have some new miners hitting your node you may want to set your share diff and pseudo share diff on your miner....


If your running S1's set to 0 ("0" defaults to lowest p2pool diff, currently 1677854.73)

And to 220.4 (optimized for 190GH/s)

is calculated as your hash rate in KH/s times 0.00000116

i.e. 190,000,000 * 0.00000116 = 220.4

Here is an example for an ant S1:


If you have a hash rate over 1TH/s you might consider upping your share diff to something higher then the p2pool minimum to reduce network traffic and increase the value of your shares...
[/quote]