Prohashing Mining Pool Forums

Thanks for that.

I hope that you've discovered a major bug with our system. The profitability numbers we're providing are those that include the hashrate declines you're experencing. If it turns out that we can fix whatever is wrong, that means we can increase profitability by 10% or more. The fact that there are profitability declines when solely mining litecoins shows that the problem can't have anything to do with work restarts.

Is there some sort of log that has debug information from Nicehash somewhere (like when blocks are found or work restarts occur), or do they not provide that?

And 40min stats for HappySatoshi

http://images67.fotosik.pl/1272/2868378100d4a528med.png

From my account level I can't find more datailed data than the charts I've published.
They offer some API calls, but seems to me that the main purpose is order management.

Thanks paszokonik I will try with those settings myself... any particular reason for r=0.2?

@tradewiz restart must be fast enough to go from initial difficulty 16 to something bigger than 1024. In other case NiceHash will report difficulty too low error. You can experiment using their Pool verificator

I am trying another setup now - it passed the pool test except it complained on the diff:
Setup: n=WorkerNicehash r=0.15 d=16384
Notice: Pool verificator is still in BETA. It may contain some bugs and it may report pool being compatible while in fact it is not compatible or vice versa.

Resolving pool host prohashing.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 98.115.147.74:3333... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received mining.set_difficulty... Pool difficulty too low (provided=16, minimum=1024)
Waiting for pool to send higher difficulty.
Received mining.notify work... OK
Received mining.set_difficulty... OK: 16384
Received mining.notify work... OK

Pool verification process is complete. Tested pool is compatible!

I am getting a delta which is too low as well..... currently about -22%. I had r=0.15
prohash reporting through 2 workers (with the same name) around 960 (but rising) - nicehash reporting around 1.8 G/h for the last 5 mins and 22% negative delta.

BTW guys I am happy to donate 0.1 BTC for you pool operators to play with nicehash yourself.... Just let me know the address... But then there is no point keeping this discussion public - I would rather that the contributing persons share information and not all the non contributing ones.....

Changed R=0.01 and still more than 10% negative delta......

In my oppinion restart time is not a key here. When I check workers history I see no restarts at all. The only restart is required at the beginning of operation in order to pump-up the difficulty.
What I can suggest to admins is to compare history from friday when I got +10% profit to today -8% loss operating with the same parameters and similar GHs unit price.