Do you have more evidence?

No such thing as "efficient for home CPUs": CPUs are not intensive compute devices. As long as the algo needs compute, it will be blasted by a proper compute-oriented architecture.

The only thing that makes sense for CPU is yescrypt, I'm surprised nobody pulled that out. Yescrypt is not compute oriented and therefore cannot be accelerated by using fast compute-oriented architectures. It is surprisingly scalable to cheap CPUs (that does not imply mining with them is profitable).

I just tried Digihash 2 miner.
I am a bit disappointed.

Let's start with a minor thing: it reads v2 but on start, version number is 1.0.1.25068. Confusing. I had to reinstall... but apparently this is correct. Maybe that was just me.

I run using the "default" settings on a Radeon 7750 with driver 14.12 Omega. I'm not quite sure who figured out those settings to target which users.

For groestl, it uses -I 17 -g 2 -w 264 on my system. Worksize 264 (256+8) is sure a sub-optimal setting for my hardware (it should be a multiple of 64). Produces a lot, a lot of output. I had difficulties figuring out what was going on.

With qubit the settings are way more sensible (-I 16 -g 2 -w 256) but it makes my system fairly sluggish but can do.

Skein goes very wrong. Leaving aside it loads both my CPU (one core) and GPU and it goes with the w 264 nonsense, the main problem is it makes my system basically unusable. When I say "unusable" I don't mean it's hard to watch an HD video on youtube. I mean it's hardly possible to edit a text file in notepad. It could be a driver issue but just to be clear, I'm not going to mine Skein ever again.

The skein miner does a thing right however: the amount of output is sensible.

Is there a "how much performance do you want to use" slider?

The "wants higher performance possible" idea is a "core miner" mindset thing. Casual users will most likely want to mine while using their computers. You should really ask them how much power they need for their job and try to not interfere with their objectives.

Last note: Groestl and Skein use an animated icon when mining. I find it very distracting. Please reconsider this choice.

I'm pretty sure last time I asked on reddit I was told the fix was still not there.

You cannot see the generated coins on the miner. If you're mining on digihash.co they'll get into your wallet. If your wallet has no coins

• Check out the configuration!
• Your hashrate could be so low you cannot even make it or, more likely
• Your GPU drivers might be messing up the whole process!

I haven't tried 2.0 yet but the previous version didn't mine by default. Did you hit the "play" ► button?

What algo are you mining and on what hardware?

I think it's worth stressing that after the BBR team noted the problem with traceability, the rest of the Cryptonote community seemed to be oblivious of the problem for quite some time. It was later declared "a minor issue" to be fixed with a "minor" GUI improvement... last time I checked (but that was some time ago) the modification was still not there. Go wonder.

Oh well, better.

I wonder if the other is using some elite kernel.

Holy crap! On verters.com, the smallest is as big as P2P-2 !

Indeed. Do you think they could have been botnets? I mean, with some degree of certainty.

I disagree.
PrettyHateMachine (sph-sgminer author) made a more than decent job, especially considering the code he had to deal with. He provided a lot of algorithms in a relatively short time frame. The precomputed SIMD_Q constants are a fairly good indicator he knew what he was doing in my opinion. It's obvious those kernels are CPU code, they are almost exactly SPHlib.

Honestly, why should anyone release hi-perf kernels since day one? He probably wasn't interested - bounties encourage first-come, low quality submissions, which in turn encourage development of elite kernels to be sold. As a side note, I have haven't improved my Qubit either and I think it has been published for over an year. I have just no interest in improving it at the moment.

Valid question! I find that very debatable.

Stuff I see here is good.

Don't use px. Try:

That sucks! Awesome move pool op.

Try to run it with no parameters at all. It will ask you to input one by one. Hopefully you might be able to see the error before it closes.
If you're using sgminer 5.x you also need to add --no-extranonce.

Brief introduction for people who doesn't spend their whole day on this forum
Some time ago I decided to practice OpenCL by writing a minimalistic miner. I decided to go with Myriad because I liked the algorithms and the idea of multi-algo, which allowed me to play a bit.
This miner has been dubbed M8M and released quite some time ago. Over those months, I've received a few bug reports by users about compatibility issues. I eventually decided to redesign part of the system.

Today mini-announcement
In an attempt to help newcomers get into mining, I decided to write a tool to check OpenCL compatibility. It is basically a mini-server and a micro-miner in the same application.

A first version has been announced on /r/myriadcoin about a week ago. The folks there helped me in identifying a few issues.

Yesterday's new version (71) adds a more accurate validity check. Shall issues arise, I will hopefully get an idea on where to look for them.

Please have a try (Windows only). If something goes wrong it'll create some .txt files. Try to get those to me via PM or in pastebin (it is a good idea to set an expire time).

Last note
I am not part of the MyriadCoin development team and this is not related to Simplicity package, even though the underlying idea is very similar.

I gave a go to digihash easy miner a few days ago. It did use sgminer 4, which does not work anymore.
Today, I see it has been updated to sgminer 5.1. Good.

Now, leaving aside that it crashes if I click the setting button before initial connection to server is completed...

This is what happens with grøstl

Here we go with Qubit:

And skein.

I blame ncurses but by the way...

I am investigating OpenCL compatibility issues across drivers and hardware. I wrote a program (oclcckvck) to evaluate kernel validity. It hashes known block headers and compares results, allowing to check mismatches by leaving the pool settings out of the equation. I think you might be interested. Please try (it just takes double click). If something goes wrong it will dump to disk some troubleshotting information; try to get them to me (I suggest pastebin with 1-week expire or PM).

Of course the final goal of OCLCCKVCK is to produce bug fixes to be integrated in next M8M release, which ultimately is meant to be a easygoing, minimal impact miner for people who use their computers to work. So  it's all about making mining more accessible and less invasive so more people can get into it.

Man we got some fine sarcasm over there. 

Makes sense to me.

Well, I can sustain your suspect as one of my contacts (who I know works in a company which pays its employees to get multiple degrees) claimed to be able to port everything in "a few days" but also that "our usual contracts are just way more profitable" so hopefully its impact is small.