Quote from: DopeLabs on August 03, 2013, 04:41:28 AM

Quote from: gyverlb on March 15, 2013, 12:47:36 AM

Known bugs/issues

Q: Why do I get lots of "Worker submitted share with hash > target:" in my P2Pool logs? It seems to put a large CPU load on P2Pool.
A: If you use cgminer, scrypt and stratum, this is because cgminer and p2pool disagree on how to represent difficulty targets on stratum. p2pool seems to use a sane definition of target difficulty, unfortunately most other pools didn't establishing a de-facto standard that cgminer follows. Current solution: use the "--fix-protocol" parameter of cgminer. It will force it to use getwork (instead of stratum) where both agree on how to communicate difficulty targets.

one of my miners is an ASICMiner Eruptor Blade, which i believe uses getwork, but i am still seeing the hash > target msgs on the cli fly by...

any idea as to why it would still be doing this considering its using getwork? and is there anything that can be done to fix?

Notice that says scrypt with cgminer which does not apply to bitcoin. Eruptors don't have any way to set difficulty, they have extremely simple mining software built in that only does diff 1. You could probably use the stratum proxy by slush between the blades and your p2pool software to get rid of the message, but not sure if that really gains you anything but adds another layer ...