Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 307. (Read 794394 times)

This is because nicehash never addressed the true cause of the original "idle bug", but only applied a hacky fix to eliminate one of its symptoms.  I had offered them the real solution to the problem quite some time ago but they declined.  And I would bet this this problem is happening to many more of their miners, but you're just one who noticed it and decided to stay and investigate rather than simply taking your hashpower elsewhere.

Everyone pointing their miners at nicehash should keep a very close watch on them to ensure that they are not unexpectedly going idle.
 

Yep, that had changed (about g4). On the command line, it had not changed. I'll try that. Thank you so much

It doesn't look right. Should be something like this:


Although -g 4 looks too high to me.

Thank you. It works now.

File sgminer-4.1.271-nicehash-9 is for Scrypt/Scrypt-N only
File sph-sgminer-4.1.0-nicehash-2 is for X11 algorithm

Hi
I download latest version of SGMiner from xxx

And have this error when start it:


the bat file is:
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u xxxxx -p x -I 13 -w 256 --thread-concurrency 8192 -g 2 --gpu-engine 1075 --gpu-memclock 1500

os: win7

Can someone help pls.

site is down.. is mining affected?

Everything is down

Website down?

I would like to know this as well.

Maybe you could try to use this stratum-proxy as a workaround (https://github.com/Stratehm/stratum-proxy/releases). I am using it for scrypt and X11 but it should work for sha-256. It works fine with the p= and d= option of nicehash.

With the DEBUG log level, you could also use it to check the stratum requests/responses of the pool and the workers.

Thankyou for the explanation. Although I would recommend this 'one time order fee' be put under the 'fees' section. Not buried in 'How to buy'
Thanks

CRYPTO MINING BLOG has written excellent and comprehensive review of NiceHash:

http://cryptomining-blog.com/2465-checking-out-the-nicehash-service-for-selling-and-buying-hashrate/

You forgot to take into account the small order submission fee of 0.0005 BTC (explained here: https://www.nicehash.com/index.jsp?p=faq#faqb0)

Let's go through an example of 1 BTC worth order:

Date UTC   TXID   Address   Amount BTC   Confirmations
2014-04-20 14:30:01   Comment: Fee order #xxx   - 0.02049
2014-04-20 14:30:00   Comment: Payment order #xxx   - 0.97951
​
The first line displays sum of all fees (one-time order-submit fee and 2% service fee)
The second line displays amount that was used to pay for your shares.

So the total amount of your order is SUM from these two lines.
​
1 - 0.0005 one-time order-submit fee = 0.9995 (amount after order submission)
0.9995 - 2% service fee (0.01999) = 0.97951 (payed for your shares)
0.0005 + 0.01999 = 0.02049 (total fees)


I hope this clarifies your case.

Thank you for using NiceHash!

So in the FAQ's it states that the fee for using the service is 2% yet I was deducted 2.49 percent for opening an order.

http://imgur.com/baoDBOg

Is my math wrong? Explanation?

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.

Is there a delay in payouts?

You will have a lot more success if you ask in PIMP thread - assuming you read the relevant howtos/faqs/etc and couldn't get it work with reasonable effort.

This is not a nicehash issue.

?

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!