I've noticed a strange behaviour. Perhaps, in some circumstances, some shares are sent to the wrong pool.
Please look at my cgminer log:
[2013-02-24 09:57:24] Switching to stratum+tcp://stratum.hhtt.1209k.com:3333/
[2013-02-24 09:58:20] Pool 0 stratum+tcp://stratum.hhtt.1209k.com:3333/ not responding!
[2013-02-24 09:58:20] Switching to http://pit.deepbit.net:8332
[2013-02-24 09:58:20] Pool 0 stratum+tcp://stratum.hhtt.1209k.com:3333/ alive
[2013-02-24 09:58:20] Switching to stratum+tcp://stratum.hhtt.1209k.com:3333/
[2013-02-24 10:03:58] Lost 1 shares due to stratum disconnect on pool 0
Where has that share gone?
HHTT pool log says:
sockthing/dub 2013-02-24 08:58:30 N H-not-zero 999 0.00000000 00000000 faacb474 815f8e93
BTW: 9:58 on my log, 8:58 on HHTT log. That's
correct, there's one hour difference.
This is why i've been able to notice it: only
999 (and above) difficulty shares should go to HHTT, and 00000000 faacb474 815f8e93 of course has a much lower difficulty. It shouldn't have gone there: most probably that nonce had been generated for Deepbit, I think, but in the meantime cgminer switched back to HHTT, so somehow the share was sent to HHTT. It's strange, too, that cgminer never logged that nonce (I mean, it never said: "... Rejected faacb474..."):
lem@biggy:~$ grep faacb474 /tmp/mining/minerlog
lem@biggy:~$
From time to time, I have some of these "H-not-zero" hashes on HHTT logs. This has been happening
since HHTT switched to stratum. I never saw an "H-not-zero" before. My only other stratum pool is slush: but slush doesn't show a log of all received shares: so I cannot know if this same behaviour is common to slush too.
I'm a bit concerned: if a 1 difficulty share goes to the wrong pool, who cares? But if one of my 999 difficulty shares goes to the wrong pool (let's say it goes to slush instead of going to HHTT, while cgminer is switching between these two pools), I'd be surely pretty sad.
Thanks.