Quote from: ocminer on August 01, 2017, 06:52:08 AM

From what i see the hashrate and shares reported / submitted by some ccminer versions are fake and therefore those versions are all not working on suprnova.

Ok, good to know. What I see is, I tried sending shares to dgbg.suprnova with 4 different versions of ccminer, all of them showed ~75% of reported hash rate disappearing somewhere. I tried sending shares to theblocksfactory with 2 versions of ccminer, and 1 of them worked as expected with miner reported hash rate and pool reported average effective hash rate being a close match.

I'm new to mining with NVidia GPUs and all the information I've found so far about Myriad-Groestl mining software for NVidia GPUs recommends some version of ccminer. Can you recommend a version of ccminer that is known to work with dgbg.suprnova? Or alternatively, can you recommend some other non-ccminer Myriad-Groestl mining software for NVidia GPUs that you know works with dgbg.suprnova?

Quote from: ocminer on August 01, 2017, 06:52:08 AM

with the static diff setting you could effectively circumvent the check and "steal" from the other miners - thats why its permanently disabled

I don't run a pool, so I won't pretend I understand what check a static diff can circumvent, or how using a static diff could lead to stolen shares. I'll take your word for it.

Good to know that static diff is permanently disabled on dgbg.suprnova. For me, static diff simplifies tuning, benchmarking, comparing mining rigs, or comparing different mining software. The rest of the time, I'm happy to let vardiff change the diff as needed.

I do have a couple of suggestions for improvements to the dgbg.suprnova dashboard.

If static diff is permanently disabled, please remove the text above the example code and the text in the -p field of the example code that tells/shows how to enable static diff. Otherwise you risk confusing and frustrating miners who are interested in using a static diff.
Since there are problems with at least 4 versions of ccminer when sending shares to dgbg.suprnova, you could help miners using NVidia GPUs who want to send shares to dgbg.suprnova by changing the beginning of the example code from ./ccminer... to ./[foldername-for-ccminer-version-known-to-work-with-dgbg.suprnova]/ccminer... or ./[non-ccminer-that-works-with-dgbg.suprnova]/[suprminer]...
It would be easier to see how workers are doing if values in the Difficulty column of the workers table matched the values that suprnova is telling the mining software to use.

I'll be back to dgbg.suprnova if/when I find software that solves Myriad-Groestl shares on NVidia GPUs in a way that dgbg.suprnova accepts/recognizes. Till then, I'll have to submit those shares to a different pool.