Hey crackfoo:

Tried the SHA256 port again last night...  Didn't stay connected long at all....   After multiple reboots too.

Just trying to get it back online here at 2:00PST, it kept being kicked off after only a few seconds...  Gave up.  Pointing elsewhere.

Very strange that my S3's when I had them wouldn't feel this issue near as much.  I wonder if the S5's do it slightly more but less than the S7....

digibyte sha256 removed?

I know its probably a tier one comment, but I have to ask:

What is line voltage at the back of the wall plug on your units when running full throttle with all gear?
Ive ran into issues with hardware frying because line voltage dropped below 100....   And I had PLENTY of overhead as far as supply wiring and such... it was a failing generator.

But.. it sounds like the hashboard has a failure of some sort.   No physical signs of burning/darkening anywhere?

It's kinda known the BM's warranty is like taking a BM.... drop it in the toilet and flush that garbage away if you expect things to happen 'right now' a failure happens.  Its always a gamble with new products with them; who knows if it will be good out of the box, or else you will need to be without it for usually weeks to a month or more... If they were a product in a store;  that would be different.  Sadly, its their strategy to protect their ass from incompetent people or ones whom dont provide what it needs to operate correctly..

you are not understanding how it all works if you are thinking that way....

To me it's just not a profitable algo for algo-switching at higher freq so I don't use it anymore, same with decred which is too slow of a coin for it as well.

I have noticed that lower hashrate connections get put on higher diff coins;  and that low diff coins are almost strictly mined by lower hashrate connections.... That's the tendency anyways.   The only low diff coins my high hashrate connections have mined have been high diff coins; except for merge-mined coins which are just taking a low diff share from a higher diff coin and submitting it with the lower diff coin.

Market fluctuations in coin prices greatly effect whats profitable as well.  Just cause it was profitable and the miner switched to it;  a dump can cause an odd lack in profit when exchanged.  Then again, there have been some crazy exchange rates in the past with select coins at random events.  People doing pump and dumps.


Point is:  The low diff coins aren't wasting hash.  AFAIK the pool is properly using each miner connection on an as-needed per-miner basis....   It would be wasteful to put a high hash miner on a low diff coin and vice versa.

Maybe crackfoo can clarify if he knows;  but he didn't write the pool code;  he's more on the coinbox config and such side of things.... where it really matters.

its simple to not mine on an algo.  do not include it in the password string, and/or your miner app config.  The pool has no control over that.

This is exactly why you can't take the reject and share rewards at face value.   Its something with the web-frontend display code;  not with the share or exchange percentage coding....

You can see the inconsistencies across the board.

So if you see this sort of thing;  please understand it's not loosing profits, it's the part of the pool that calculates each value to display to you that has an issue.

Hopefully these vales will help getting down to the cause of where the fault(s) are...   And I am wondering if any other pools using this interface/code are seeing the same type of issues....

Got back from SF finally after almost a week.

Miner was up and running producing steady shares.   Backed off intensity for machine usability and restarted the app.  Now the pool sees and reports it as a connected miner.

The whole time it was not shows as a connected miner, but the summary showed 0 connected miners at ~2% share rate and ~28-32Mh.

Something else I noticed earlier that this was if you compare the table just below the summary, it shows a different share percentage, as well as a different share percentage of the block reward.

There has to be some sort of issue with the pool web-end which stems down to them not having the calculation done by a child function;  instead they are coding it on a per-need basis and one of those on many algos are flat-out calculated wrong.

The final payout and rewards seem to be correct and consistent with the past, and the way the market has been going recently as well (BTC worth more, miners paid less;  because people tend to base price off power usage for some not so insane reasoning)....  Its bound to happen.

Maybe I am totally wrong and am not here to debate it, just saying I am getting near what I expect (I take my expectation and payout usually is +/- 12-20% on average.

It's just reject calculation for display that's off as far as I can tell.

So my card has been locked on lyra2 for several days now (by choice) and it gets lots of reports of being offline yet shares keep rolling in at the proper rate.

Thought I'd comment.


Profitability for me has been somewhat down a touch across the board, but I am no longer running any SHA at all on zpool; sold my personal miners < s7, and the s7's are pointed at NH and solo.

No comments on skein removal but I also yanked it from my machines in SF just today.

This is what setting I used when I tried this morning and never got an accepted share within a few minutes, only two rejected shares.

spent 30 min trying to get an app with it to no avail.    gave up.

I see the scryptn port was just turned on.... as I now see the 4 posts above this one =)

I can't find any support in any release of ccminer.   What a shame.

For instance;  Skein seems to poop out lots of low value blocks... which is totally fine... but it deosn't get as many high value coins out except in groups.  So when the profitability spikes, it switches only to not see the gains as if you were on the algo the entire time.   Kinda like when the miner switched to decred for a few min here and there.   The reward down the line after you are switched off it and a block is finally found; is pretty minimal.

*edit*

Also, I have found the best switching algo combo to be X11evo, X14, X13, X17, X15 and neoscrypt...

A side note to see if anyone feels the same...

skein just doesn't seem to earn enough... maybe its the algo switching and the larger value coins don't come in regularly enough to keep it profitable.  I have seen my average slowly decrease since adding all the algos so I think I may be pulling it from the batch;  but I will leave the code at the bottom for people to paste in if they want to use it.

Interested on any others opinions....

I see no problems.   Please be more specific on what blocks, what algorithm, if it's mining or exchanging, etc.


I am seeing regular block generation on my rigs right now.

So, I added V1.03 to the original post where I update the batch.

I need to figure out what happened as the process detection isn't working with the 3rd algo.  At first thought it's probably a long filename issue, so I will need to do some testing.

I suggest people whom have used 1.04 to go back to 1.03 where it was reliable.   I will report back when I have figured it out.

God help me when it comes to simple things related to microsoft that don't work when you do them correctly.

Snap.  I tested with default intesity and didn't transfer that setting to the final batch.  Try removing the -I and (I believe) the setting of 17.5 from the "start %C% /min %C1%....." Line...  Also the comma and diff setting after the %PASS% section on the same line.  Should "uncork" it.

I'll remove all these personalizations when I get back home in a few hours and post it as 1.4.1

*edit*   Looks like the intensity and difficulty are not set and default... did you by chance happen to download it right as I posted it?  I found a small bug right after posting it and changed the code a few min after...  Probably should have noted it...   But I dont see why you would be seeing reduced performance otherwise...

I had a very strange issue with trying a new utility to force my card into P0 state... which helped... but, my card is still getting kicked into P2 by ccminer....  At least the settings for P2 are now locked at full speeds and I gained ~3Mh on lyra2.  Havent checked how the others were effected.

Done and Done.  Thanks for the pointer!   Happy to report hashrate (at my current "to have a usable PC" backed off intensity) Increased from 9.6Mh to 23.7Mh.  Current app filename was: ccminer_nanashi_lyra2rev2.exe  Downloaded Nicehash miner V. 1.6.0.1

I have updated the miner batch to reflect this with V1.04.  If you wish to update, first visit this link:
https://github.com/nicehash/NiceHashMiner/releases
And download the latest version of the nicehash miner.  As mentioned above, unpack the folder that the ZIP includes, and you will find the lyra2v2 optimized version in the ./bin folder.  Copy it only to your regular miner app directory where the batch is and you are set to go.

This is a major change, only because if people want to stay with the non optimized versions, they will need to re-assign the C variable to reflect your normal miner app, and you will also need to change the normalization in the password string to be the old value of 9.6.   Seeing the performance boost (more than 100% more hashrate) I don't see why you would not want to update.... Plus hopefully I can just release a main ZIP file of all miner apps wrapped up, and release any updates as just copy and replace type of deals in the near future.

I have noticed on small screen resolutions that in my signature the miner batch link isn't always able to be shown.  In that case: Click here to get to my batch file.

So I was having issues with getting devices older than my GTX980 to work with the recent miner apps.

Sadly, None of the newer ones seem to support the older devices.... except the X11evo release mentioned a few pages back.

So if you would like to use the batch with older cards, let me know and I will strip down a copy as to fit within the password length limit to only include the most profitable algos.

Currently I am able to get ~1.4Mh out of the watercooled EVGA GTX 560 I got handed to me recently on the X11evo algo.

However;  I didn't modify the batch, so when it finally switches to an algo that is further down the list than the password allows, multiple algos will stay connected at the same time.

I will experiment with re-ordering the variables as to let this happen as little as possible on its own without any major modifications to the batch....

Anyone else in this same situation?



Also, is there anyone here with a windows X64 machine that has the programs and libraries to compile a miner for me?  I would be tickled pink if someone could take that X11eco fork of the ccminer-DEV version to accept the longer passwords and make the batch truly universal....


If someone can point me to the GTX980 optimized Lyra2 version as well.  I used to have an optimized version (GTX980 I was seeing 12-14Mh back when zpool first opened last year, but hearing the 8Mh->20+Mh jump for the nvidia cards has me intrigued)....   Basically I am starting to get motivated to add all the optimized versions to this batch as to make it as versatile and as efficient as it could ever be.

Once I have a master stable conglomerate of miners and the batch all in one place, I will find somewhere useful to host it so people can just download it as an entire package instead of having to find the miners like I have been.

If people want to help me assemble a list of version numbers, fork name, for different algos that are optimized in CCMINER ONLY (I am trying to stay on a one-track road with config strings)  Please comment them here and Ill build up the list and take the necessary steps to get them all together for the public to know and have access to easily.

I know it will be tough staying up to date with bugfix version releases, but honestly, I think its time to just step up to the plate and do it myself to save face for the rest of you.


I got rid of all of those ATI cards (at the request of my friend since he's going purely nvidia now) so if someone else could do this for the ATI side (if needed) I will work with them to get a similar batch and miner package together for that as well.   Maybe even if its useful and in enough demand it will be linked on the site for the newcomers as well... but I think that is reaching beyond my grasp for now

At my home (The RV) I am stuck to a single circuit, so I want to maximize what I can pull off this free electricity; since an underclocked S7, and my PC running full-ham is enough draw to drop my line voltage from 110 to 102.2.....   Any more draw, and Ill be dipping into a very uneasy place....  I almost melted my power cable when I added 2 S3's for half a day....

But I know it can handle the uncorked S7 and the PC 24/7 just fine....  But if I want to do something like run the microwave, something is getting shut off for a few min... lol

I think just biting the bullet and going only with the newer gen equipment will be the best option in the future.   Once I upgrade the S7 here, Ill just move it to the warehouse in SF.

I have been eyeballing the S7LN's for a bit now.  I just sold bolt of my last S3's, so S7's are the oldest tech I have working out of everything.  My parents are going solar within the next few months (putting in a 5.8Kw system) so ill sit and make a deal with my father so I can put in a second meter, power point and distribution so i can set up some miners on a rack in their garage.... just pay them the power every month and half the profit to see if I can get my father into buying some new ASICS

He's a retired hardware engineer so I think I can get him on-board... (designed the first GPS for trimble, of which I still posses the first ever fully functional final-design prototype that has the military decryption built in [its a big deal to have the mil-spec decryption.... pinpoint accuracy with one device and no reference station], also designed the first ip phone for Cisco Systems, and the list goes on....)

Awesome news.   Yeah, That's about right, cause i tend to pull in ~66mBTC (or ~8-11mBTC/day) give or take every week with just an S7 on Nicehash.   If I was at home more often, I would be having it pointed at zPool instead;  because it constantly needs me to hard reset it when the pool disconnect bug kicks it into stupid mode.  And this S7 is underclocked to 3.5Th so I can run the fan at 32% and temps hovering between 60* at night and as high as 75* during the day.  Gotta keep the noise to a minimum so the landlord doesn't wanna charge me more rent for the power..... lol  Luckily I have an unused roof vent that I duct the outputs to, so temp control is a breeze.

One of the downsides to living in an RV....  But at the same its an upside for sure!