Static diff does not work and your vardiff algorithm is buggy, (for digibyte-skein) at least.
setting
-p d=1.536
works, for a while and sets the difficulty at 1.536 and then vardiff kicks in and changes it.
vardiff keeps increasing the difficulty until the miner submits nothing for a a few minutes. After not submitting shares for a few minutes vardiff drops the difficulty a notch, and I can see 1-2 shares if it gets lucky, and then bumps up difficulty again -> no shares -> lower a notch -> 1-2 shares -> increase -> rinse and repeat.
in 2 hours of mining with same test hardware, the block factory earned 120 DGB while mining pool hub earned 14 DGB, this is fudged up. (Yes, 120 vs 14 it is not a typo)
In the test hardware there is a mix of 1080/1070/1060s and vardiff setting the difficulty to something over 8, even 1080(~1GH) cannot find a share. I'm curious what the vardiff algorithm is targeting for..
Sorry static diff is temporarily disabled due to misuse of some users attacking server.
I'll change some and open it again.
What is your total hashrate anyway? 14 is quite low even considering that PPLNS penalized your shares.
Enabled static diff feature for Digibyte
You can set static diff by setting sd=XXX text at miner's password.
e.g.) sd=8
can someone please check this for skein-DGB, it does not work at all for me
ccminer-x64 -a skein -o stratum+tcp://hub.miningpoolhub.com:20527 -u xaq.london -p sd=2.048 --scantime 1
Sorry static diff is temporarily disabled due to misuse of some users attacking server.
I'll change some and open it again.
your vardiff algo pushes difficulty too far too soon and stays there for a long time, it is almost unusable without static diificulty for me.
This is a test machine i use to check different algos accross different GPUs. ıt has a 1080, 1070 and 1060 can't remember the exact hash rate now, but something like 1.6GH
18DGB in any case almost unreal, the problem is when the diff is over 8 miner can't find any shares to submit until the difficulty drops back. A very rough difficulty cycle looks something like this
3->6->8->6->7->8->7->8->7->8... And these are not equal time periods, 8 takes quite some time, while lower difficulties gets bumped up very fast as soon as miner starts finding shares. So practically miner submits shares at less than 20% of the total mining time.
I am curious why no1 else complained about this may be it is an issue with ccminer or the mixed cards i use or may be both.