[ANN] cpuminer-opt v3.19.7, open source optimized multi-algo CPU miner

[JayDDee]

This is the home of cpuminer-opt, the optimized CPU miner.

Supporting over 90 agorithms with many optimized for CPUs with the latest technologies:

Intel Haswell: AVX2
AMD Zen3: AVX2, SHA and VAES
Intel Skylake X: AVX512
Intel Rocketlake: AVX512, SHA, and VAES
Intel Alderlake: AVX2*, SHA, and VAES

Older 64 bit CPUs with SSE2 are also supported, see below for requirements.
*Alderlake is a hybrid CPU architecture with AVX512 disabled.

Downloads

Source code and Windows binaries are avaiable for download.
Download only from the official JayDDee git repository.
There may be malware masquerading as cpuminer-opt, stay alert.
I no longer post links in new mesages and I don't post direct links to files. Any such links should be treated
with suspicion. The only valid download link is below and directs to a landing page that can be examined
for legitimacy before any files are downloaded.

Latest release including Windows binaries
https://github.com/JayDDee/cpuminer-opt/releases

Documentation
https://github.com/JayDDee/cpuminer-opt/wiki

List of supported algoritms
https://github.com/JayDDee/cpuminer-opt/wiki/Supported--Algorithms

Source code
https://github.com/JayDDee/cpuminer-opt

New in v3.19.7

#369 Fixed time limited mining, --time-limit.
Fixed a potential compile error when using optimization below -O3.

New in v3.19.6
#363 Fixed a stratum bug where the first job may be ignored delaying start of hashing.
Fixed handling of nonce exhaust when hashing a fast algo with extranonce disabled.
Small optimization to Shavite.

New in v3.19.5

Enhanced stratum-keepalive preemptively resets the stratum connection before the server to avoid lost shares.
Added build-msys2.sh shell script for easier compiling on Windows, see Wiki for details.
X16RT: eliminate unnecessary recalculations of the hash order.
Fix a few compiler warnings.
Fixed log colour error when a block is solved.

New in v3.19.4

#359: Fix verthash memory allocation for non-hugepages, broken in v3.19.3.
New option stratum-keepalive prevents stratum timeouts when no shares are
submitted for several minutes due to high difficulty.
Fixed a bug displaying optimizations for some algos.

New in v3.19.3

Linux: Faster verthash (+25%), scryptn2 (+2%) when huge pages are available.
Small speed up for Hamsi AVX2 & AVX512, Keccak AVX512.

New in v3.19.2

Fixed log displaying incorrect memory usage for scrypt, broken in v3.19.1.
Reduce log noise when replies to submitted shares are lost due to stratum errors.
Fugue prehash optimization for X16r family AVX2 & AVX512.
Small speed improvement for Hamsi AVX2 & AVX512.

Win: With CPU groups enabled the number of CPUs displayed in the ASCII art
affinity map is the number of CPUs in a CPU group, was number of CPUs up to 64.

New in v3.19.1

Changes to Windows binaries package:
 - builds for CPUs with AVX or lower have CPU groups disabled,
 - zen3 build renamed to avx2-sha-vaes to support Alderlake as well as Zen3,
 - zen build renamed to avx2-sha, supports Zen1 & Zen2,
 - avx512-sha build removed, Rocketlake CPUs can use avx512-sha-vaes,
 - see README.txt for compatibility details.

Fixed a few compiler warnings that are new in GCC 11.
Other minor fixes.

New in v3.19.0

Windows binaries now built with support for CPU groups, requires Windows 7.

Changes to cpu-affinity:
  - PR#346: Fixed incorrect CPU affinity on Windows built for CPU groups,
  - added support for CPU affinity for up to 256 threads or CPUs,
  - streamlined code for more efficient initialization of miner threads,
  - precise affining of each miner thread to a specific CPU,
  - added an option to disable CPU affinity with "--cpu-affinity 0"

Faster sha256t with AVX512 & AVX2.

Added stratum error count to stats log, reported only when non-zero.

Full change log: https://github.com/JayDDee/cpuminer-opt/blob/master/RELEASE_NOTES

Requirements:

1. A x86_64 architecture CPU with a minimum of SSE2 support. This includes Intel Core2 and newer and AMD equivalents.
AES optimizations require a CPU with AES_NI including Intel Westmere and newer and AMD equivalents.
Further optimizations are available on some algorithms for CPUs with AVX (Sandybridge), AVX2 (Haswell, Ryzen),
AVX512 (Rocketlake, Skylake-X), SHA (Ryzen, Rocketlake), and VAES (Zen3, Icelake).

32 bit CPUs, ARM CPUs, Intel Atom, Raspberry PI, etc, are not supported.

Mobile devices are not recommended because they aren't designed for continuous full load.

2. 64 bit Linux OS. Ubuntu and Fedora based distributions including Mint and Centos are known to work and have all
dependencies in their repositories. Others may work but may require more effort.

Windows 7 or newer, 64 bits is supported using the pre-compiled binaries package or may be cross-compiled using a Linux
system with mingw.

FreeBSD is not actively tested but should work, YMMV.
Apple and Android operating systems are not supported.

Older CPUs, other architectures and operating systems may be supported by TPruvot's cpuminer-multi.

Security warning

Miner programs are often flagged as malware by antivirus programs. This is usually a false positive, they are
flagged simply because they are cryptocurrency miners. However, some malware has been spread using the
cover that miners are known to be subject to false positives. Always be on alert. The source code of cpuminer-opt
is open for anyone to inspect. If you don't trust the software don't download it.

Some cryptographic code has been taken from trusted sources but has been modified for speed at the expense of
accepted security practices. This code should not be imported into applications where secure cryptography is
required.

Errata:

Old algorithms that are rarely used or are too difficult to mine with a CPU will not get the latest optimizations.

Cryptonight and variants are no longer supported, use other miners.

Hodl requires a CPU with AES, use legacy version if without.

Donations

cpuminer-opt has no fees of any kind but donations are accepted.

BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT

[1653044582]

1653044582

[1653044582]

1653044582

[1653044582]

1653044582

[joblo]

Just a quick note to reassure readers that although JayDDee is a newbie user here
we are the same person. The new userid now matches my github userid.

[Iamtutut]

Posting here to get the updates on the new thread.

[Dabs]

You could also change the signature on the older account to match the new thread.

[JayDDee]

You could also change the signature on the older account to match the new thread.

Thanks for the reminder. I intended to do that although I won't be posting much from that user anymore.

I'm more interested in adding a sig to this user once the newbie training wheels come off.

[joblo]

You could also change the signature on the older account to match the new thread.

Done.

[Elder III]

Even if CPU mining isn't always profitable, it's still excellent to have a miner that works with so many algos, even if just for testing purposes. I appreciate all the work you have done over the years on this miner.

[impynick]

Thank you for your contributions to CPU mining. As an avid cpu miner I appreciate the options your miner brings to the table

[JayDDee]

I've created a wiki page for cpuminer-opt. It's all one page with no index, sorry but I don't know how to make it more structured
other that breaking it up into seperate files.

Users may want to scroll past the first half, it's just copied from README files. The interesting part is the log report descriptions
that start about half way down.

A lot of changes have been made to the miner's displayed output and a lot of new info is provided. I attempted to make it as intuitive as
possible while prioritizing and highlighting the most important points. I also tried to limit redundancy by not displaying the same data
in different forms or statistics that can be easilly derived from other displayed data. The data can be used with data obtained from other
sources to provide even more advanced info. For example, block reward and coin exchange rates are not known to the miner but
when combined with pool and exchange data can build a full profitability profile.

The new log reports were the result of 2 minds: the geeky user who wanted all the data available, and the developper who wanted to provide
the data in the most efficient manner, as raw as possible while still being understandable to a moderately experienced user.

It's all here...

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

It's still rough around the edges, lots of typos and missing topics, buit it's a start.

[chrysophylax]

Still at it mate ...

You are still sitting in my 'highest respect' list. Always looking forward to what you may be doing next.

Massive updates to the codebase I see also.

This profile will be a legend in no time

#crysx

[JayDDee]

Nice to hear from you Chrys.

Mining isn't what it used to be but writing SW keeps me out of trouble.

I've kinda lost touch with you and chainworks, how's that going? It seems like you're always
exploring new ventures.

[JayDDee]

cpuminer-opt-3.12.4.3

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

Solo mining with getwork is now working again with improved log reporting.
Edit: fixed segfault in getwork from v3.12.4.2.

See RELEASE_NOTES for detailed changelog.

[JayDDee]

cpumminer-opt-3.12.5

This release should bring an end to the flurry of releases recently to address problems with share statistics
for both getwork and stratum mining. Stats should now be correct and robust with the ability to verify many
mining performance parameters.

A list of variants of yespower algorithms and parameters has been added to README.md. These algos can
be mined by cpuminer-opt simply by specifying their parameters.

See OP for more info.

[chrysophylax]

Nice to hear from you Chrys.

Mining isn't what it used to be but writing SW keeps me out of trouble.

I've kinda lost touch with you and chainworks, how's that going? It seems like you're always
exploring new ventures.

Always nice to see all that is happening with you mate ...

Especially the positive, even though negative is always part of the equation.

CWI is doing a LOT. Mostly backend stuff and not stuff I really want to bring out here in public. You know what happens if even a small amount is leaked out, then taken considerably out of context. Two years have passed since the reset and continuation of theFARM, and that is going strong, renting some of the units through MiningRigRentals under the CWI-Rental banner, with a new Mine (Rebuild of Amethyst Mine) underway for all areas of mining. New codebase being built for the template of the coins we have to rebuild, and ultimately being integrated into one MasterCoin we have codenamed CoinX for the time being.

CPU mining is one of our goals for Amethyst Mine and I assure you, even though mining is not what it used to be, it is still as exciting as it was when it first started.

Never in any case has the memory of your help in the background when I was stumbling at the time of compilation and understanding, has left my mind. Your help THEN has always been a reminder that decent people exist in Crypto. Always that respect mate, no matter whether we see eye to eye or not (and I fail to remember when it was not - but there you have it).

What you have done with CPUMiner-Multi is amazing. CPUMiner-OPT is in a league of it's own now. The leaps and bounds is well worth the time and effort to reacquaint yourself with the coding world, and a huge success it seems to be. I do see at times you get frustrated, but that comes with the territory mate. We all do, especially with the trolls.

There is much to do and still a long road to tread, but as long as we tread and cut the road ourselves, we follow in no others footsteps, and that my friend, are steps worth taking.

As for CWI, a lot more has happened in the background and the plans are seemingly coming to fruition this year. All the puzzles' pieces shall fit some time soon in the big picture. One thing is for sure though, if there is anything that we can do together, my door is always open to you.

New Ventures for us are also backend mostly, and can discuss with you privately, but none of them are small. We have become a very precise instrument, nay a tool, to deal with all we have undertaken, and hone it all into an enterprise that is worth the long (almost 9Year) effort I have personally invested in Crypto thus far. We have 'good' people with us, and they are doing great things. That door is also open to you.

Keep doing good things JDD (JoBlo or whatever Pseudo you wish to use) - as you usually do mate.

#crysx

[orlandoblim]

Can we discuss about the price?

[Saisher]

I was redirected from my thread asking about my hardware for mining, is it still profitable mining with CPU I see a lot of algo that is compatible to this mining software but can it compete and what's the best coin to mine using this software, do you have a video tutorial for your software.

[JayDDee]

Benchmark is broken in cpuminer-opt-3.12.6. It will be fixed in the next release.
Mining is not affected. Use v3.12.5 for benchmarking until the fix is released.


Edit: v3.12.6.1 is released with benchmark fixed.

[chrysophylax]

I was redirected from my thread asking about my hardware for mining, is it still profitable mining with CPU I see a lot of algo that is compatible to this mining software but can it compete and what's the best coin to mine using this software, do you have a video tutorial for your software.

I think ...

I think that these questions really should be directed to a trading (read - gambling) thread about price and the trade systems.
I think that that you should know the differences between coins and what they do, or don't do in most cases, and what the benefit is of those coins distanced from 'money'.
I think that who ever creates applications, improves them and optimizes them (like this project), and continues to do so, is adding more value to Crypto itself, than to the 'price' that most of you out there are so obsessed with.

Who cares about price? Most of you that are out there fumbling their way trying to do the complete opposite of what Crypto was actually designed for, by trying to make more of the money that enslaved us all in the first place.

Who cares about the Technologies? The people that care about the optimization and improvement of such technologies and the development of such things for the betterment of Crypto. Like this project.

Who cares about value in Crypto? We should ALL care, but very little do. Price and FIAT (Governement OWNED cash) is all that most care about, meaning not many have a good grasp of what Crypto really is about.

So when you ask about 'price', 'profitability', and whether sofwtare 'competes' in this arena, you are asking the wrong questions in the wrong place. This thread is about the optimization, development, and GROWTH of the code and application, than the 'price' something is, which is a moot subject here.

It saddens me to see Crypto over the 9Years I have been around in this 'scene', to watch the idea of 'freedom' get turned into 'slavery' because all you want is to turn Crypto into Cash.

Crypto = Freedom/People.
Cash = Government/Slavery.
CPUMiner-OPT = development.

Who gives a damn about the money other than those that lust for it? I sure as hell don't, and I can gurantee ANYONE that knows what Crypto is about and respects the core values of Crypto, is the same. So please don't smear this thread and the 'clean' talk of development and functionality with the filth that 'price' and 'cash' and 'profit' always end up doing.

JDD = keep hammering away at the code mate. You are doing an AWESOME job!

#crysx

[JayDDee]

I was redirected from my thread asking about my hardware for mining, is it still profitable mining with CPU I see a lot of algo that is compatible to this mining software but can it compete and what's the best coin to mine using this software, do you have a video tutorial for your software.

So when you ask about 'price', 'profitability', and whether sofwtare 'competes' in this arena, you are asking the wrong questions in the wrong place. This thread is about the optimization, development, and GROWTH of the code and application, than the 'price' something is, which is a moot subject here.

Hear! Hear!

I've made it clear in the past I don't give advice on mining, only technical information.
And I don't compete.

[p2501]

Any chance you could help with the following error during compilation?
This is under centos 6 and gcc 8.3.1

util.c: In function ‘send_line’:
util.c:1136:15: error: ‘sock’ undeclared (first use in this function); did you mean ‘work’?
      n = send(sock, s + sent, len, 0);
               ^~~~
               work
util.c:1136:15: note: each undeclared identifier is reported only once for each function it appears in