Coins come and go too quickly, it would be too much work to try to maintain such a list. Go visit some pools
to see what coins they offer and what algo they require. There's a good chance cpuminer-opt supports it.
Some pools also display the coins' profitability.

Oh dear, I've seen this too much. Here is what I know.

Sometimes when a miner stops and restarts, usually to switch algos, it will exhibit any of the following symptoms:
    - it will fail to start with the same parameters
    - it will start with reduced intensity (-i)
    - it will start in a degraded state, low clock

A reboot will correct the problem.
The occurrance appears to be random. Sometimes a card will get hit multiple times per day, sometimes not for several days
Only some cards are affected, some never exhibit the problem.
There is no pattern to the affected cards, Maxwell and Kepler have both been affected.
It occurs on Windows and linux.
It does not appear to be driver related.
It appears to affect only specific individual cards.

There was discussion about this several months ago. A search on "degraded" might find something.
The bottom line is it was never solved. It's possibly a HW issue.

I do have some new information, It may be heat related, possibly heat stressing a marginal component.
I recently moved an affected card to the basement where it's cooler. It had been crashing often when
profit switching. Since the move it has been more stable but I have not been profit switching with it. I only
switch manually every few days. I may setup profit switching on this PC to try to recreate the problem.

Well there ya go. It's one of those things that has been nagging me for a while. I feel better now.
You could try swapping the cards to see if the problem moves.

Follow the link in my sig and look at the chart. Your core2 CPU does not have AES_NI so you can't
mine any algos that are AES_NI only. You can mine any coin that uses a supported algo and there
are over 25 supported algos.

I'm glad you caught that one yourself.

However, there does seem to be an issue with coin selection. On several ocasions I have seen sigbnificantly
lower profitability coins getting more hash than higher profitability coins. It would make sense hi the hiprof coin
was small and can't handle a spike hash spike but I have seen  it when the high prof coin is the biggest coin
in the pool. In such cases it should get all the hash, shouldn't it?

A specific extreme example occurred a couple of days ago with quark. DNET, the biggest coin in the pool
was paying twice what SAK was paying but SAK was getting more hash. That shouldn't happen. In fact all
coins in the pool were getting a lot of hash. DNET's share was less than 50% of the hash even though it
represents about 70% of the pool's value.

BTW at the same time the other yaamp clone was 100% DNET.

What do you mean there's no way? It's just part of the password string like any other password.

I appreciate the hard work, I've done a lot in the past couple of months. I know a lot of it has been
cut & paste but there is original work also. But hard work doesn't sell a product.

For the 3% increase you are offering one would need 3 970s to break even. That would give 9%
increase for 10% of the price of a 970 compared to 100% increase for 100% of the price of a 970.
I'm not big enough yet.

Sure. Use whatever password/coin you want just like you were mining directly.

I've got 2 CPUs mining HOdl, a i7-6700K running Linux and cpuminer-opt, and a i7-4790K running win8
and hodlminer-wolf. Both clocked at 4 GHz and mining 8 threads. They both produce around the same
hashrate as reported at the pool, around 200 H/s. It fluctuates a lot so it's hard to be precise.

If I can get similar rates as Wolf0, without his optimisations I should be able to do better. That will have to wait
until tomorrow.

Crypto Mining Blog has both the Wolf0 and original hodlminer versions compiled for windows.

You need to set your price very very low. Do your own comparison, you can expect the decred factor to be
around .000n times x11.

Simply choose an algo as a reference and divide the hashrate on the target algo by the hashrate on the reference:

Ex: x11 = reference = 1

decred factor = decred hashrate / x11 hashrate

Or you can pick your own reference, many profit switching pool use AMD factors which, in many cases, do
not apply to Nvidia.

I get 18.5 quark on a EVGA 970 with +100 OC with the FOS version. Hard to justify paying .1 BTC. How much are
you holding back in your super-private version?

It depends on the algo and whether there is a miner available for the device. ASICS are available for sha256, scrypt
and recently x11. SHA256 andscrypt are hopeless with anything less. X11 hasn't yet taken a hit from the introduction
of the ASIC for it.

GPU mining is most efficient for most other algos and CPU mining isn't really worth it. However, there are a few
algos designed specifically to be difficult to implement on a GPU or ASIC. Some have a poorly performing GPU
miner or none at all. Look around the forum, there's always discussion about it, and be sure to use cpuminer-opt.

Wolf0 has me beat. I don't know if I can do any better, probably very little if anything. I'll have to look into
the local hashrate issue, it's not a problem with other algos.

Since I used the original hodleminer and Wolf0 has added AES_NI optimisations I guess I'll put the two
together and support both CPU architectures in one miner, along with all the other algos that cpuminer-opt
supports.

Full credit to wolf0 for his AES_NI stuff!

Am I arriving late to this party?

cpuminer-opt with HOdl support now in beta.

I'm getting around 400 H/s on i7-6700K @ 4 GHz. How does it compare?

Edi: pool reports about 60% of the hashrate cpuminer-opt reports. This puts my performance in line
with hodlminer.

Currrent beta version of cpuminer-opt also works on non-AES_NI CPUs.

Greetings. I realize the prize has been taken but I have something that may be of interest.

I have been developping an optimized CPU miner for a couple of months (see sig) and have
now implemented hodl support. My hashrate on a i7-6700K is around 400 H/s. This seems to be
quite a bit better than some others I've seen. It will be available in v3.1.10 very soon.

It will only be available as source compileable in Linux. I know there is a lot of demand for Windows
but that's not my thing. Anyone is free to grab the source and try to get it working for Win.

I'm not doing this for money but if my improvements are significant it might be worth something.
There could also be motivation for someone else to get it working on Windows.

Edit: Also with without AES_NI

I just signed up to your pool to test HOdl support in cpuminer-opt but haven't set a payout
address yet. Will that cause any problems? I could donate the test hash to the admin unless
I get serious about mining HOdl.

BTW I'm getting 400 H/s on a i7-6700K @ 4GHz, 8 threads. How does that compare with others?
With hodlminer I get about half that.

Stay tuned, to be released soon.

Not a problem as long as you use powered risers.

I don't think -i is the only thing you're looking for.

If you have infrequent share submissions which causes the to pool report a widely fluctuating hashrate you can smooth
it out by lowering the diff encoded in the password argument on yaamp clones (ie "-p d=0.5"). This will also vary
by card with bigger cards being able to handle a higher diff. Too low causes excessive network traffic and rejects.
It's easier to verify hashrate when it's more stable.

Edit: more specifically diff varies by rig hashrate and bigger rigs can handle higher diff.

-i, or intensity is a way to max resource usage on cards and, as crysx said, varies by card. SP has tuned the defaults
for most maxwell cards pretty well but you can play with it to see if you can squeeze out a bit more hash. If it's
set too high ccminer will crash. Just try with a lower value.

Seems to be a common falacy. There's lots of FUD about the BTC block halving in a couple of months driving the
price down.

Is this legit?

I don't see this version on your releases page. Someone recently posted having downloading an infected
miner from CMB so I'm suspicious.

http://cryptomining-blog.com/7679-updated-ccminer-1-7-6-fork-by-tpruvot-with-improved-decred-support/