Doesn't that already exist?
log in to p2pool and append /SHARECHAINTARGET+WORK_TARGET
e.g.
./cgminer -o something.pool.com:9332 -u mineruser/5000+16 -p none
that will return 5000 difficulty work to the share chain, and it will only serve 16 difficulty work (instead of "1")
log in to p2pool and append /SHARECHAINTARGET+WORK_TARGET
e.g.
./cgminer -o something.pool.com:9332 -u mineruser/5000+16 -p none
that will return 5000 difficulty work to the share chain, and it will only serve 16 difficulty work (instead of "1")
Not sure if you'd know but ...
Seems to me there's some mileage in setting the difficulty to higher than the defaults if only to reduce network latency? I've started tinkering around and setting to minername/512+1 and it seems that 'Bitcoind GetBlockTemplate Latency' has reduced slightly since then.
Since getting that latency average down as low as possible is one of the only things you can do to improve p2pool returns (afaik), this seems to be an overlooked tweak?
I might also be being a bit dumb, but what's the point of setting the difficulty higher than the current valid accepted share difficulty? It's at 1300 at the moment for example. So any share submitted over 1300 should count.
And finally .. me also not understanding something (yes I have tried to!), if I've set 512+1, then why is it still returning 1/1 to 511/1 difficulty shares to the pool? Or have I got that the wrong way round?
Basically I'm puzzled by the difficulty settings and there ain't much documentation on it that I can find.
PS. Note to Litecoin miners. If it's giving you so much grief on p2pool, why not forget Litecoin and concentrate on Bitcoin? Seems to me that if you want BTC to retain value for all the BTC you mine, then sticking with BTC is the way to go long term rather than supporting a slightly less secure competitor for what basically seems to be greed.
PPS. Note to people freaking out because p2pool throws some errors and pauses a while to figure it out. Stop staring at the p2pool screen! I've only seen pauses like that near the initial startup while p2pool is easing in to the network. I guess it may happen while I'm asleep after running for hours, but if it does, it recovers, it goes on churning away, I maybe loose a few minutes. I've never yet checked it the next morning to find it's died, it's always happily churning away.
Well, first off, yeah, I was wrong about the 2000 cap, just got a 2005 share. Maybe the person up above that said the max adjusted based on current difficulty was right, or maybe it just got bumped up, I dunno. It also seems to be providing me with 5000 difficulty shares, so I assume that'd work too if it ever picks one up (the whole New work for worker! Difficulty: 10.000000 Share difficulty: 5000.002049 thing).
A 2600 share will count for twice as much as a 1300 share, the only difference would be that it'd increase deviation, but should average out eventually. For someone at 5-10ghash+, 2000 isn't bad. For someone at 20ghash, 3000+ would be neat. Why? Because p2pool is set to balance out as much as it can to 6 shares a minute... so, for the person at 300mhash, the 1500 difficulty shares aren't so nice. If more people set theirs higher, then the share difficulty would drop, and this huge variation wouldn't occur for people mining on one card or something. Right now it's spitting out 1327 difficulty shares, so 511 or w/e wouldn't do anything. You'd still have to get the 1327.
oh, heh, I just got a 4.82k share on that one that's looking for 5000
