[ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool

[gruevy01]

Is there something wrong with the difficulty?  Ever since the problems with the X11/X13 yesterday, my difficulty settings are being ignored.  I've set d=0.01 but difficulty stays at 0.04.
I've tried changing my difficulty but it stays at 0.04.

[nicehashdev]

We are now running with higher difficulty until the problem is discovered and resolved.

[TheMoen]

Would it be possible to return orderid when a new order is created with the API?

[nicehashdev]

Would it be possible to return orderid when a new order is created with the API?

Will be available with next deployment of frontend.

[djbert]

I have been providing SHA256 hashing power for some time on the site, but for the last 24 hours my SHA256 miners haven't been receiving any work. I don't have the minimum price set, so i thought it was related to the DDOS attack, but that has passed already. All my SHA256 mining software connect to the site, just no work is being given. So is anyone having these issues??? I also provide x11 hashing power, but that is working just fine. I am located in Japan. Thank you!

Am I the only one with this problem?? i have been provide hash power on SHA256 for quite some time, and now i am not getting anymore work. i have changed nothing on my end, no settings/ports or software. what is going on? my x11 miners are chugging along just fine....

[suchmoon]

nicehashdev, I posted a reply for you in the profitability thread, reposting here just in case. This is debugging output from cudaminer.

* Rebuilt URL to: http://stratum.nicehash.com:3333/
* Adding handle: conn: 0x7f994c013e80
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 1 (0x7f994c013e80) send_pipe: 1, recv_pipe: 0
* About to connect() to stratum.nicehash.com port 3333 (#1)
*   Trying 91.223.115.35...
* TCP_NODELAY set
* Connected to stratum.nicehash.com (91.223.115.35) port 3333 (#1)
* Connection #1 to host stratum.nicehash.com left intact
[2014-06-18 10:43:23] > {"id": 1, "method": "mining.subscribe", "params": ["cudaminer/2014.02.28"]}
[2014-06-18 10:43:23] stratum_recv_line failed
[2014-06-18 10:43:23] ...retry after 15 seconds

[torontominer]

anyone stuck on waiting for work available from the pool
as long as use p=0.7；d=0.01 as passwd and payout rate fall under 0.7
the miner never switch to backup server


please help

[Lubo77]

Hello

All my miners report that stratum servers for SCRYPT(3333), SHA256(3334), SCRYPT-N(3335) and KECCAK(3338) are dead.
Only X11 and X13 are working. Same for 4xxx ports.

I am located in Slovakia.

I have used traceroute to determine connection and only X11 and X13 returned results.

Anybody can help?

[nicehashdev]

Should be fine now for all miners that couldn't connect.

We have raised minimal difficulties for both providers and buyers. Providers can now use diff 128 or higher for scrypt, nscrypt, sha256 and keccak, 0.04 or higher for x11 and x13.

Buyers have to use pools that support min diff 32 for scrypt, nscrypt, sha256 and keccak. We are in era of fast ASIC and it is simply unacceptable for pools to still have so low difficulties (imagine how many diff 32 shares a 80MH/s scrypt ASIC sends, if one simple 500KH/s card can already produce 1 share per 10 seconds). If your favorite pool does not support higher diffs, we suggest you to contact them and explain that they are loosing important money on fees that they could gain when just increasing their diff (which is one setting in config file).

[chococat211]

hi nicehash dev, me and my friends getting disconnect problem, around 2 to 3 hours (give or take) we cant connect to Nicehash (or Nicehash disconnect with us), if we want to reconnect we have to reboot modem to get new IP, after modem reboot - got new IP, we can connect to Nicehash just fine (we using dynamic ip internet).

This problem start after DDoS and maybe because of you starting ban IP with too many reject (my reject always 2 to 5% and I tried all the way but cant get my reject lower -if someone know please tell me, thanks), is there anyway for us to avoid this disconnect problem, its really annoying to wake up at night each 2 to 3 hours to reset modem.

P/S: me and my friends live same country but we use diff ISP and we live in diff town so this cant be internet problem.

[Stinky_Pete]

Hi
This is my first try with Nicehash but I'm having problems contributing SHA-256 hashing
I am using Windows 7 and bfgminer 3.10.0 or 4.0.0 (makes no difference)
I just get a constant stream of -
"Stratum from pool 0 requested work update" alternating with "Rejected untracked stratum share from pool 0"

Is it me or something poolside?

[kenshirothefist]

Important! You should set appropriate difficulty for your miner to increase efficiency and reduce the number of submitted shares that produces rejects. If you have fast miner that is capable of creating masses of rejects at short time, then set higher difficulty so the reject count is lower, otherwise your miner might get banned by our overload prevention system. One thing to remember is that difficulty doesn't affect earnings. Higher difficulties will result in lower bandwidth and less frequent shares submission. You can set the difficulty of your miner by setting d= within your password parameter to one of the following values: https://www.nicehash.com/index.jsp?p=faq#faqs7

[chococat211]

Important! You should set appropriate difficulty for your miner to increase efficiency and reduce the number of submitted shares that produces rejects. If you have fast miner that is capable of creating masses of rejects at short time, then set higher difficulty so the reject count is lower, otherwise your miner might get banned by our overload prevention system. One thing to remember is that difficulty doesn't affect earnings. Higher difficulties will result in lower bandwidth and less frequent shares submission. You can set the difficulty of your miner by setting d= within your password parameter to one of the following values: https://www.nicehash.com/index.jsp?p=faq#faqs7

Tyvm FIY, I have 50 rigs 3x290, my total hashrate ~500MH, I'm using d=0.01 now, if I only mine x11 and x13 then do you have any suggest which diff should I set?

[uberua]

Should be fine now for all miners that couldn't connect.

We have raised minimal difficulties for both providers and buyers. Providers can now use diff 128 or higher for scrypt, nscrypt, sha256 and keccak, 0.04 or higher for x11 and x13.

Buyers have to use pools that support min diff 32 for scrypt, nscrypt, sha256 and keccak. We are in era of fast ASIC and it is simply unacceptable for pools to still have so low difficulties (imagine how many diff 32 shares a 80MH/s scrypt ASIC sends, if one simple 500KH/s card can already produce 1 share per 10 seconds). If your favorite pool does not support higher diffs, we suggest you to contact them and explain that they are loosing important money on fees that they could gain when just increasing their diff (which is one setting in config file).

We are now running with higher difficulty until the problem is discovered and resolved.

Is there something wrong with the difficulty?  Ever since the problems with the X11/X13 yesterday, my difficulty settings are being ignored.  I've set d=0.01 but difficulty stays at 0.04.
I've tried changing my difficulty but it stays at 0.04.

There are no ASICs for x11 and x13 so as I understand it was not an explanation for these algos...
Could you answer pls when it will be solved for X11 (X13)?
Thanks.

[Vizakenjack]

Would be nice if past orders groups by pool url && pool port && pool username && pool password.

So instead of 10 little orders without date and pagination, I'll be able to find how much did I spent for certain pool

[kenshirothefist]

Tyvm FIY, I have 50 rigs 3x290, my total hashrate ~500MH, I'm using d=0.01 now, if I only mine x11 and x13 then do you have any suggest which diff should I set?

You should adjust difficulty for each separate miner (rig), that said, if you have multiple rigs, each rig with 3x R9 290 that makes about 10Mhs for X11 per rig, and if you look at this table this results in a suggested diff d=0.08. Even if you're mining with several rigs at the same BTC address, you should set diff for each separate rig, not for the combined hashing power of all rigs.

[alienesb]

why do my rigs can't connect to x11 and x13 servers ? i tried all port : 4337,3337,4336,3336

Yep, trying to get a new rig up and am having the same issue.

[mrp1]

I just placed 1 order for limited GH/s of .05, they were excepted THEN I noticed they were assigned a .10 GH/s and were eating through my $$ at TWICE the rate I had contracted for !!!   CAN'T change the rate on the order screen, it won't accept anything less than .10 -  I then created another order at .05 and the SAME deal !!!   What's up   False advertizing !!   (PS - It was OK yesterday - what's changed and WHY ) !!!

[mrp1]

VERY FUNNY....  Just noticed you changed the website to .1 !!!   Don't bother answering my prior post !!!   NOT A HAPPY CUSTOMER ..

[uray]

i can't put order for 0.05 GH/s speed !?
what the fuck, yesterday it was OK, i wasted my hashrate, since Mineral pool are limited to 50 MH/s and we are in rush hour before PoW end, don't u see there are a lot of 0.05 GH/s customer on the list !

NOT a happy customer ! move back to betarigs