This is brilliant ... and NiceHash.com you *REALLY* ought to add this!!

CSA1234 can you post a specific link that shows where this is paying?  Is this GridCoin related?

Looks like it just happened again?

Hey ... what just happened to all of my X11 stats?

The last 7 days+ just got wiped clean?  All gone?

UPDATED:

Oh ...  NiceHash @NiceHashMining: We had to reset all provider stats (graphs) to fix the issue regarding stats. Again, no BTC is lost. We are sorry for the inconvenience.
 :-(

Are we any closer to getting some JSON APIs for NiceHash?

I'm after two things if possible:

1. An API to get the home page stats for each algorithm.

2. An API to get my miners last {x} stats ... the ones you chart on the miner stat page.  Specifically, I'd like to get my Accepted Speed as an array of values so that I can compute an average over the time period.

With these two values I can begin to autoswitch my miner between algorithms for profitability.

I don't want to write another HTML scraper ...  :-)

There is a *new* and *different* bug that is impacting cgminer v3.4.2a+ and NiceHash ... I'm experiencing it on numerous boxes, and am trying to find a fix.  This is *NOT* the "idle bug" or it is not completely fixed in cgminer.

I'm mining SHA and when running using the "price" option in the password - p=0.07 - and letting it run for long periods of time, suddenly the NiceHash pool will appear in the miner as "Alive" ... but the pool is not passing any work, and the threshold has NOT been hit!  There are NO contracts for 0.07 ...

This is now easily reproducible on more than one box, and they are running the latest cgminer that does contain the "idle bug" fix.

I am trying now to debug the protocol, and determine exactly *WHY* cgminer would believe - when sending the miner.subscribe and miner.authorize requests - believe that the pool is alive.

When this happens my miners are sitting idle - believing they are connected to an active pool, but not being given any work.  Today I have lost hours of mining when I have come back to check the status of my miners and found them in this state.

I have reached out to NiceHash, ckolivas and kano for assistance, but any other assistance in debugging the protocol or cgminer would be appreciated.  Until I can know exactly how NiceHash is handling the protocol requests, it is very difficult to debug cgminer to see what is going on.

When you get me a JSON API I'll see if I can give you a Windows app that will control the miners and restart them with the proper algorithm.  I'll bet I can talk the PiMP team into supporting the same for Linux!

kano/ckolivas,

I'm working with the guys at NiceHash.com to try and resolve a few issues with how they are managing miners with their stratum pool.  In debugging this, I've been reading through the code that implements the stratum client - util.c - and trying to better understand the stratum protocol.

What I'm not quite clear on is the loop/state machine that you use in a mining client to "poll" a pool and attempt to connect to get work.

The NiceHash.com pool uses the password parameter in a mining.authorize to pass in a requested "threshold" for mining payouts.  (e.g. I might only want to mine if there are contracts for a minimum of 0.07BTC/TH/Day so my password becomes "p=0.07")  When the mining.authorize occurs, they will accept or error my auth based on that threshold comparison.

This is working ... mostly.

The problem we are seeing is that at some later point of time, the miner seems to "hang" or believe the pool is alive.  I'm running kano's builds on my AntMiners, and periodically during the day I'll find them attached to the pool, but not getting any work.  They think the pool is alive ... the pool is saying they sent an error on the auth.

I am debugging to see if this is pool related, miner related, or protocol related.  (Or a little of several?)

What I wanted to know is:

Within cgminer, once a pool is determined to be "dead", what is the delay before the pool is tried again, and what operations (Requests) are retried to "test" the pool for aliveness?  Where would I find the code that handles that delay and retrying?

I'm writing here, as I tried to locate and study the protocol documentation to determine what the "proper" process ought to be ... but didn't find too much on the subject.  :-)

I'm wondering if a miner like cgminer would be doing :  mining.subscribe -> mining.authorize -> error/delay/startover-at-subscribe?

If this is the case, is there any reason to believe that after looping like this - getting errors for a half day or so - the miner might hang?

I'm also glad to take this conversation elsewhere if this is not the appropriate thread.

Here is what you have to consider:

1. You need to "baseline" your hashrates on your cards, mining each different Algorithm.
2. Using these baselines (e.g. Scrypt: 3.2MH/sec, X11: 9.2MH/sec, etc.) you then need to calculate against the numbers on the home page.
3. For example:
  - Scrypt: 3.2 MH/sec = 0.0032 GH/sec * 3.2698 BTC/GH/Day = 0.0104 BTC/Day
  - X11: 9.2 MH/sec = 0.0092 GH/sec * 2.3073  BTC/GH/Day = 0.0212 BTC/Day

So at the moment, mining X11 is far more profitable ...

This is why I want the JSON API to retrieve the values and automate the calculations throughout the day.  Then I need to control and relaunch my miner - pretty easy to do - altering the conf file to switch Algorithms based on these calculations.

Is there a JSON API for the stats on the home page?

I want to be able to fetch the Statistics table of the four Algorithm pools without having to scrape the page?

I'm working on a way to autoswitch my miner between configs, to switch from Scrypt to X11 and back based on calculated profitability with my hash rates.

Hello,

I wanted to say there is still an issue with NiceHash and cgminer.  I'm still trying to narrow down the specifics, but here is what I am seeing from my side:

1. I have two identical AntMiner S1, both running the updated cgminer (Kanoi builds) v4.3.2a
  - https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

2. I have both configured with pools identically - the primary pool is set to:
 - stratum.nicehash.com:3334
 - {my address}
 - p=0.065;d=128

3. I have secondary and tertiary pools defined - Eligius and GHash.io

4. Today, when the contract ran that was 0.08 they both switched to NiceHash properly.

5. When the contract completed, and then next was 0.06, both AntMiners went to the second pool - Eligius - as they should have.

6. About an hour ago, you had a contract for 0.07 show up ... and I noticed it showed as Alive and Dead ... on and off.  Both AntMiners mined, and fell back, several times ... but then one fell back to Eligius and the second hung mining nothing.

7. You home page showed the 0.07 contract dead ... that AntMiner still showed the pool alive.  It was mining nothing for 4-5 minutes ... and then I restarted it.  Once I did that the pool showed dead ... like your home page did.

I've checked the code in Github, and the Kanoi builds for the AntMiner have the same fix as ckolivas for the idle bug:

https://github.com/kanoi/cgminer/blob/master/NEWS#L25


Would you expect that when you have a bad contract/pool that I would see the miner hang for that long?

===================================================================================

I'm adding this about an hour later ... same thing just happened to my OTHER AntMiner ... I noticed it was stopped mining on both pools!!  NiceHash as the first priority was showing as ALIVE in cgminer ... even with my threshold of 0.065 ... with no contracts visible.

Why?

I had to restart the miner ... and NiceHash went to "DEAD" ... now it's working again.

++10 !!

It would be great if there was a way to set "per pool" parameters - within the "pools" section of the conf file - and allow these to override the "default" parameters when that specific pool became active.

This would have many benefits, but primarily allowing for switching pools between completely different algorithms.

Please anyone have a way to do this?

Is there a way with sph-sgminer to set "per pool" parameters?

I want to make my primary pool NiceHash X11 - using the darkcoin kernel - and then have my backup pool be NiceHash scrypt -using the zuikkis kernel ...

I'm trying to find a way to allow the pools to each be defined with their own set of unique parameters to allow this.

Ideas?

What is the calculation for diff when mining X11?

For example. .. if I've got 10MH/sec of X11 hashing ... what would be the recommended?

d=??? in the password?

Kano replied and linked to those exact fixes being in his cgminer ... he's maintaining it exactly.

https://github.com/kanoi/cgminer/blob/ants1-4.3.2a-85fcf0c/util.c#L2048

There must be some other bug.  :-(

My two test AntMiners ran fine on the pool ... switched to the backups when the thresholds were too high ... but then at some point the NiceHash pool went Active again, but nothing was mining.

Crap!

I have verified with kano that I am running cgminer v4.3.2a  commit 85fcf0c ... what version is ckolivas saying this is fixed in?

I want to get my Ant farm over on NiceHash ... but with this bug it keeps leaving my Ants not mining anything!  :-(

I also wrote to Kano again with a private message to inquire about the fix.  I asked if he was aware of the fix done by ckolivas, and if he had brought that into his fork.

kano ... have you incorporated the "idle bug" fix in your builds that is mentioned here?

I'm using the latest cgminer from user "kano" who wrote to you above ... he has been making the builds for the AntMiner S1.  Do you have details of the fix/build that ckolivas made so that we can ensure that kano adds it?

Bummer.  There are still some strange issues going on with my AntMiner S1s working against the pool with "price" thresholds.

I just came home and found my two test AntMiner S1s hung ... they *said* the NiceHash pool was alive ... but they were NOT mining it ... and they were NOT mining my backup pools.

Both were mining earlier in the day, and then when the 0.06 contracts expired, they fell back to the backup pools.  That is where they were when I left the house.  I come home and realized they were in some strange state ... not mining NiceHash nor the backup pools.

I had to restart the miners, and then they immediately jumped back to the backup pools as there are no 0.06 contracts.

Something is broken ...

Ha ha ... at 0.05?  SHA mining at those prices is more profitable elsewhere ...