The official miner of the coin is in the wallet. Does your docker image contain wallets, making the docker
image a GUI front end to manage a bunch of wallets running on the user's computer?

Managing multiple wallets is not for newbies no matter how much you try to make it look easy.

If you're serious, a wallet manager would be a good product but not as a docker image full of your
selection of coin wallets. It should be a regular program using a web server interface or a custom
GUI front end. In the back end the user should be able to install any wallet they choose.

This would not be for newbies because newbies use online wallets or exchanges instead of installling
a wallet for every coin the they mine. Only coin geeks do that.

This thread smells really bad.

First red flad: newbie

Second red flag: a registered account is required

Third red flag: closed source software

Fourth red flag: no description of what the product actuallly is or does, just marketing doublespeak.

Fifth red flag: slick marketing targetting aimed directly at newbies

Sixth red flag: instructions to enter cryptic commands without disclosing they download and install software

Seventh red flag: BS claims about being CPU only and about a "universal miner".


...

cpuminer-opt-3.9.1.1 is released

Fixed lyra2 regression affecting non-AVX2.

Compiling on Windows using Cygwin now works.

Simply use "./build.sh" from a cygwin shell.

I have no list of likely packages that need installing on top of the base Cygwin
installation. You'll have to wing it for now.

It isn't portable therefore the Windows binaries package continues to use
the existing procedure.

As always please report any problems.

cpuminer-opt-3.9.1 is released

https://github.com/JayDDee/cpuminer-opt/releases

Fixed AVX2 version of anime algo.

Added sonoa algo.

Added "-DRYZEN_" compile option for Ryzen to override 4-way hashing when algo
contains sha256 and use SHA instead. This is due to a combination of
the introduction of HW SHA support combined with the poor performance
of AVX2 on Ryzen. The Windows binaries package replaces cpuminer-avx2-sha
with cpuminer-zen compiled with the override. Refer to the build instructions
for more information.

Ongoing restructuring to streamline the process, reduce latency,
reduce memory usage and unnecessary copying of data. Most of these
will not result in a notoceably higher reported hashrate as the
change simply reduces the time wasted that wasn't factored into the
hash rate reported by the miner. In short, less dead time resulting in
a higher net hashrate.

One of these measures to reduce latency also results in an enhanced
share submission message including the share number*, the CPU thread,
and the vector lane that found the solution. The time difference between
the share submission and acceptance (or rejection) response indicates
network ltatency. One other effect of this change is a reduction in hash
meter messages because the scan function no longer exits when a share is
found. Scan cycles will go longer and submit multiple shares per cycle.
*the share number is antcipated and includes both accepted and rejected
shares. Because the share is antipated and not synchronized it may be
incorrect in time of very rapid share submission. Under most conditions
it should be easy to match the submission with the corresponding response.

Removed "-DUSE_SPH_SHA" option, all users should have a recent version of
openssl installed: v1.0.2 (Ubuntu 16.04) or better. Ryzen SHA requires
v1.1.0 or better. Ryzen SHA is not used when hashing multi-way parallel.
Ryzen SHA is available in the Windows binaries release package.

Improved compile instructions, now in seperate files: INSTALL_LINUX and
INSTALL_WINDOWS. The Windows instructions are used to build the binaries
release package. It's built on a Linux system either running as a virtual
machine or a seperate computer. At this time there is no known way to
build natively on a Windows system.

Attention Ryzen users.

It is well known that Ryzen has a HW implementation of SHA and also well known that
Ryzen also added AVX2 capabilities. Unfortunately Ryzen's AVX2 performance is poor.

The combination of these 2 points makes for some unusual effects on some algorithms
depending on how much sha256 they use and how much AVX2 they use.

An extreme example is the sha256t algo, which is pure sha256 and also supports 8-way AVX2
and 4-way SSE.

The hw SHA implementation can't do parallel so the 8-way and 4-way code uses sw sha.

On Intel CPUs the performance is very predictable, 8-way AVX2 is fastest, 4-way SSE2 is next
and 1 way is slowest.

On Ryzen it's the reverse. the single stream using HW SHA is fastest. A 16 thread Ryzen 1700
using HW SHA outperforms an 8 thread i7-6700K 8 way AVX2 by 50%. The 4 way SSE2 code is
just as fast as, and maybe a little faster than, 8-way AVX2 on Ryzen. And the AVX2 performance
is downright pitifull in most cases. Th eonly case where AVX2 may perform better is in
4-way AVX2 where there is no SSE2 equivalent.

As previously mentioned the impact depends on the mix of SHA and AVX2 in the algo
as well as whether SSE2 parallel hashing is available.

I will investigate further and provide recommendations for Ryzen users.

The solution may extend beyond compiling and may require some code changes to ensure
Ryzen prefers SHA over n-way when the algo contains a significant amout of sha256.

It likely won't be the upcoming release.

Edit: Here's a list of algos that use sha256

sha256t: as described above.
lbry: significantly affected but less than sha256t
skein: similar to lbry.
m7m: no 4-way, not a problem.
yescrypt and yespower: no 4 way, not a problem.

Don't trust this guy, or this miner. It's a ripoff of cpuminer-opt and he didn't publish thes source code.
For all anyone knows it may have a hidden dev fee or even worse. Stay far away from this one.

Here's a tease. It's the only visible part, much more is going on behind the scene.
I'm trying to streamline the process, reduce overhead (especially interleaving for
4 way) and new innovative (imo) ideas for increasing performance. For now it's still
in the napkin stage but it's starting to take shape. It means increasing the parallelization
beyond the size of the largest vector. I have no idea if it will incease performance or
by how much. It may actually be a flop but I think the idea has merit. It's a bit of a twist
on another idea pioneered by a long time miner developper with an explosive name.
That's all for now. I have a bug fix someone is waiting for I'm almost ready to think
about a new release, still a few days away.

It looks like lyra2Z. Have you tried it?

A lot of good advice above.

CPU mining is a good place to start without needing to buy new HW like a big GPU.
All your CPUs listed can run cpuminer-opt with varying levels of optimization.

You won't make any money but you can get some experience before you invest
in serious hashpower.

Make sure your CPUs are clean and make sure your cooling is adequate. CPU mining
is one of the most CPU intensive applications in existence, and things get pretty hot.
This goes for GPUs also.

Avoid laptop PCs due to heat and accelerated battery wear, and avoid gimicks like
browser mining and Android apps.

Use a trusted miner application and a real desktop CPU.

Time-limit is the only one that exits, the others like max-diff, max-temp just wait at idle.

It was a new algo and it's changed already, yet another reason why I don't like it.

This seems to be a trend: vertcoin, zcoin, cryptonight, ...

It appears to be an anti ASIC strategy, with SW miners able to adapt quicky without
requiring new HW.

It's not that big of a deal for a single coin but daunting for a multialgo miner to keep up.
That the race I've withdrawn from.

TPruvot has it, does it work better? I've already looked at the code.

My first glance shows it's a completely new algo and can't benefit from any of the canned
optimizations. To optimize it requires a detailed analysis of the code to look for opportunities to
vectorize either serially, parallelly, or not at all. I expect the scalar code to be near optimum already.
It's a huge task to do the whole algo at once. Not really interested at this time.

Hashrate displayed by the miner, both thread and share, are artificially
calculated based on the number of iterations over time. The pool calculates based on the number and
difficulty of submitted valid shares. Perhaps there's a math error in the miners calculations.

cpuminer-opt-3.9.0.1 is released.

Fixed a problem where cpuminer could hang at startup on Windows 7 and server 2008.

https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.9.0.1

Thanks for posting. It appears to be a problem with Win7 & Server2008.
Win8+ & Server2012+ should bre ok. I'm working on a fix.

Not likely this year.

The problem is I don't have one, still waiting for Cannonlake or whatever Intel decides
to release and when the decide to release it. SkylakeX is too old and too expensive for
me and I'm only one year into my Ryzen.

Now that I'm back I have a slightly different approach to the project.

What it comes down to is I will do WTF I want. If something doesn't interest
me I may be dismissive. My currrent inerests are focussed around vectorization
of Intel/AMD CPU architecture. I am not a cryptography expert I can't write crypto
algorithms from scratch from a spec.

I welcome algo requests bu I will only add new algos that suit me. Factors include
its popularity, availablility of compatible source code, and potential for improvement.
If it's already in cpuminer-multi it's a plus.

I will no longer support cryptonight or any of its variants. It's too much work just to keep
up and there are other faster miners available.

A reminder that I don't accept git pull requests. I do all dev offline and only upload releases.
I you have a code update you would like submitted please discuss with me first by opening
a git issue or posting here.

Happy mining.

Thanks, needed a break. Reasons are too many to list but all crypto related, mostly I was demotivated.

cpuminer-opt v3.9.0 is released.

https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.9.0

Added support for Windows CPU groups. (not available in precompiled binaries)
Fixed BIP34 coinbase height.
Prep work for AVX512.
Added lyra2rev3 for the vertcoin algo change.
Added yespower, yespowerr16 (Yenten)
Added phi2 algo for LUX

I can't help with the Phi issues. Once they are sorted out I can look at any cpuminer issues.

Should be in the next release.